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

search_path should not affect schemas #134

Closed

Conversation

mzabani
Copy link
Owner

@mzabani mzabani commented Mar 24, 2023

Fixes #133

mzabani added 3 commits May 3, 2023 17:39
This ensures fully qualified object names end up in the
representations, which is nice, but more importantly, it ensures
the schema is immune to the user's search_path setting.
@mzabani mzabani force-pushed the issue-133-search-path-should-not-affect-schemas branch from 247fa21 to 5eb27f4 Compare May 3, 2023 21:02
@mzabani mzabani marked this pull request as ready for review May 8, 2023 20:02
@mzabani
Copy link
Owner Author

mzabani commented Jul 17, 2023

This has been superseded by #147, which creates class constraints like InTxn and NotInTxn.

@mzabani
Copy link
Owner Author

mzabani commented Jul 17, 2023

This has been superseded by #147

@mzabani mzabani closed this Jul 17, 2023
@mzabani mzabani deleted the issue-133-search-path-should-not-affect-schemas branch December 14, 2023 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SQL schema specification inconsistencies
1 participant