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

(feat) #15 Add support for database schema setting #16

Closed
wants to merge 5 commits into from

Conversation

leonardb
Copy link

@leonardb leonardb commented Dec 8, 2013

nfldb should be installable in a non-public schema if desired,
this commit sets the search_path for the cursor so that all queries
will be against the desired DB schema first and public second

Squashed commits:
(feat) Add support for database schema setting to config file
(feat) add a PFX replacement mechanism for DDL
Simple string replacement on all DDL in the db module to allow
for explicit resource references in DDL updates
(fix) correct use of new conn tuple
(fix) bad call of pfx fixed
(fix) spaces do help

nfldb should be installable in a non-public schema if desired,
this commit sets the search_path for the cursor so that all queries
will be against the desired DB schema first and public second
nfldb should be installable in a non-public schema if desired,
this commit sets the search_path for the cursor so that all queries
will be against the desired DB schema first and public second

Squashed commits:
(feat) #2 Add support for database schema setting to config file
(feat) closes #3
(feat) #1 add a _PFX_ replacement mechanism for DDL
       Simple string replacement on all DDL in the db module to allow
       for explicit resource references in DDL updates
(fix) #1 correct use of new conn tuple
(fix) #1 bad call of pfx fixed
(fix) #1 spaces do help
@BurntSushi
Copy link
Owner

I'm just chiming in to say that I intend to address this, but don't yet have the time necessary to devote to it. I'm hoping I'll get to it next week. Thank you!

@BurntSushi
Copy link
Owner

My apologies for taking so long to give this a more careful look through, but I really don't want to merge this as-is. It touches a ton of code and clutters up every single query with a magic string. I don't think I want to maintain that going forward.

However, I don't want to put you out either. It seems like you might be able to fix this with a solution outside of nfldb: http://stackoverflow.com/questions/2875610/postgresql-schema-path-permanently --- Do any of those solutions work for you? If not, why? Maybe we can figure something else out.

@BurntSushi
Copy link
Owner

I've just completely gutted the nfldb.Query implementation, so this PR I think is as good as dead for the time being.

I'd be happy to work with you to solve whatever problem you're having though. Please file a new issue!

@BurntSushi BurntSushi closed this Jul 22, 2014
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.

2 participants