You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Copy of Original of Email:
"
i am trying to work out if the system can handle reads and writes for a Postresql db.
For handling writes, you normally need to be constantly parsing the WAL. I can only see a SQLite implemenation of that.
I guess you use the SQLite only as a proxy for all the other databases.
My main aim with your system is to enable us to have many databases and to validate what is coming out of them.
on the read side for queries i am curious if you allow pass through, so clients can make a SQL query and its all just passed through magically to the database.
Its a bit hard with the currnt code to work that out.
the Test Net in docker and linearizability is pretty smart. Reminds me of "Call me Maybe" DB testing.
"
To build larger systems on top, you need to react to changes in the system.
For example maybe you want to build some microservices, and they need to know when a CUD ( Create, Update, Delete) occurs on the underlying data so that they can be triggered to do whatever they need to do.
Describe the solution you'd like
A golang based solution.
A simple JSON stream.
We spoke on Gitter about Redis, but it would also be good if its not tied to that because these days there are so many other ways of doing pub sub, like NATS, Kafka, etc.
Describe alternatives you've considered
Well there are no other ways other than polling form the top down into the DB and that is just not going to scale.
Additional context
We spoke on gitter about this use case and feature request, so the context is there.
Cant see a way to get an anchor link into the part of gitter where we discussed this, so just have to put the link to the room here: https://gitter.im/CovenantSQL/CovenantSQL
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Copy of Original of Email:
"
i am trying to work out if the system can handle reads and writes for a Postresql db.
For handling writes, you normally need to be constantly parsing the WAL. I can only see a SQLite implemenation of that.
I guess you use the SQLite only as a proxy for all the other databases.
My main aim with your system is to enable us to have many databases and to validate what is coming out of them.
on the read side for queries i am curious if you allow pass through, so clients can make a SQL query and its all just passed through magically to the database.
Its a bit hard with the currnt code to work that out.
the Test Net in docker and linearizability is pretty smart. Reminds me of "Call me Maybe" DB testing.
"
To build larger systems on top, you need to react to changes in the system.
For example maybe you want to build some microservices, and they need to know when a CUD ( Create, Update, Delete) occurs on the underlying data so that they can be triggered to do whatever they need to do.
Describe the solution you'd like
A golang based solution.
A simple JSON stream.
We spoke on Gitter about Redis, but it would also be good if its not tied to that because these days there are so many other ways of doing pub sub, like NATS, Kafka, etc.
Describe alternatives you've considered
Well there are no other ways other than polling form the top down into the DB and that is just not going to scale.
Additional context
We spoke on gitter about this use case and feature request, so the context is there.
Cant see a way to get an anchor link into the part of gitter where we discussed this, so just have to put the link to the room here: https://gitter.im/CovenantSQL/CovenantSQL
The text was updated successfully, but these errors were encountered: