Repository navigation
How do we customise the tables that apalis will use? #40
Description
Activity
Could you actually describe the issue you are facing? Have you given the setup a try? I ask that because
apalis-postgresuses its own schema ie the jobs table is fixed atapalis.jobs. This should ensure you dont have any conflicts.I will admit that I have not tried running it locally because I was worried that it might mess with my local testing data (took me a lot of time to setup my local db). I wanted to try giving it a prefix before I set it up, but wasn't able to find anything in the docs.
Thanks for the info about the schema separation. Perhaps this should be added to docs.rs? Happy to put a PR for this if you'd like
Reacted by Njuguna Mureithi
Metadata
Metadata
Assignees
Labels
No labels
Is there a way to give apalis a table prefix or something that can be added to the table name, such that we can share the postgres tables with our main backend? This way, if we use a common connection string (frequently used in managed database services) with the main application backend (the primary data store for, say, user data), we can prevent collisions with table names.