Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use prisma transactions for write queries to correctly automatically rollback in error situations #300

Open
chiragjn opened this issue Aug 11, 2024 · 1 comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@chiragjn
Copy link
Member

See: https://prisma-client-py.readthedocs.io/en/stable/reference/transactions/#usage

@chiragjn chiragjn added good first issue Good for newcomers help wanted Extra attention is needed labels Aug 14, 2024
@jalotra
Copy link

jalotra commented Sep 8, 2024

This is a good one, giving some context for dev working on this :
Creation of a collection is 3 step process :

1. Create a postgres row in table : "collections"
2. Create a vector document in vector db, defaults : "qdrant"
3. Then Associate the collection created with associated data sources.

Say if step 2 was failing, which was the case as I didnt looked that profiles --profile ollama and --profile --dev was needed, same collection cant be made 2nd time; as postgres already knows that this collection exists.

dhananjay-srivastava added a commit to dhananjay-srivastava/cognita that referenced this issue Nov 4, 2024
…ion manager and updated prisma store to use transaction manager if supplied
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants