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

Default schemas should now be utilized when describing tables (this real... #812

Merged
merged 1 commit into from Aug 9, 2013

Conversation

2 participants
@durango
Member

durango commented Aug 9, 2013

...ly only affected Postgres users for the most part) and fixed sqlite/mysql having trouble with dropping the correct schemas. Closes #672

Default schemas should now be utilized when describing tables (this r…
…eally only affected Postgres users for the most part) and fixed sqlite/mysql having trouble with dropping the correct schemas. Closes #672

durango added a commit that referenced this pull request Aug 9, 2013

Merge pull request #812 from durango/describe-schema
Default schemas should now be utilized when describing tables (this real...

@durango durango merged commit 75fce70 into sequelize:master Aug 9, 2013

1 check passed

default The Travis CI build passed
Details

@durango durango deleted the durango:describe-schema branch Aug 9, 2013

@josdewitte

This comment has been minimized.

josdewitte commented Jun 29, 2014

Dear Durango,

could there be an option like "schema" or "schemaName" for postgres dialect also like you made for SQLite? Currently query-generator.js for postgres showTablesQuery hard-codes 'public' schema thereby overriding default login schema for a certain user, and since all my tables are in a specified schema any existing table import results in 0 tables since they are not in schema "public".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment