feat: wrapper connection implementation
Problem
Describe the problem you are trying to solve here
Solution
Provide a brief summary of your solution so that reviewers can understand your code
Environment variable changes
What ENVs need to be added or changed
Pre-deployment activity
Things needed to be done before deploying this change (if any)
Post-deployment activity
Things needed to be done after deploying this change (if any)
API changes
| Endpoint | Method | Request body | Response Body |
|---|---|---|---|
| API | GET/POST, etc | request | response |
Possible Issues in the future
Describe any possible issues that could occur because of this change
A couple of things.
- What is happening to the prepared statement objects in postgres? Are we creating them everytime? And if so are they being GC'd?
- How are we planning to handle schema changes during the execution of flow? For instance, during workspace setup we want to first create the workspace schema, ran from inside the
publicschema & then switch to thesuperpositionschema for inserting into theworkspacestable, all in one transaction. - Can we please add the debug logs for each query based on an env as well? That would be a very useful thing to have.
- Can you add tests that verify that things are working as intended?
I am seeing that we don't need the .schema(..) DSL w/ this, we might just be able to move back to standard diesel!
... 4. Can you add tests that verify that things are working as intended?
I can do the tests part if something is taking time.