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

Add support for having nfldb in non-public schema #15

Open
leonardb opened this issue Dec 8, 2013 · 3 comments
Open

Add support for having nfldb in non-public schema #15

leonardb opened this issue Dec 8, 2013 · 3 comments

Comments

@leonardb
Copy link

leonardb commented Dec 8, 2013

nfldb should be able to reside in it's own database schema.

This should include all domains, types, tables etc

@leonardb
Copy link
Author

leonardb commented Dec 8, 2013

See pull request #16

@leonardb
Copy link
Author

leonardb commented Dec 8, 2013

I think in the long run wrapping the various execute functions in the cursor to do the replacements may be a cleaner option, but I'm at a bit of a loss as how to achieve this when an 'extra' cursor type (Dict I believe) is being used.

I would think maybe approaching it in a similar manner to the logging cursor, except parsing and rewriting the query may work.

@BurntSushi
Copy link
Owner

It seems like you might be able to fix this with a solution outside of nfldb: http:https://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.

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

No branches or pull requests

2 participants