Closed zenoran closed 3 years ago
Hello, I am Blathers. I am here to help you get the issue triaged.
It looks like you have not filled out the issue in the format of any of our templates. To best assist you, we advise you to use one of these templates.
I was unable to automatically find someone to ping.
If we have not gotten back to your issue within a few business days, you can try the following:
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.
I'm having a hard time understanding the exact problem being described in this issue. Can you provide a more concrete example of how the search_path behavior is violating your expectations?
I'm having a hard time understanding the exact problem being described in this issue. Can you provide a more concrete example of how the search_path behavior is violating your expectations?
My apologies! I meant to post this in the django-cockroachdb repo!
Is your feature request related to a problem? Please describe. The problem is having all the tables dumping to the public schema
Describe the solution you'd like Ideally to have an option available within the database engine config to specify a schema
Describe alternatives you've considered search_path appears to be effective but it requires modifying the create_cursor method in DatabaseWrapper and also modifying the get_table_list in DatabaseIntrospection.
Additional context I think it would be fairly easily to integrate this through a parameter passed within the database connection (similar to other DB engines), but I was wondering why it wouldn't have be done yet? Having the basis of the engine to be dumping all tables within the public schema seems a bit odd. Unless I'm missing something?
Thanks!