Skip to content

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

Merged
durango merged 1 commit intosequelize:masterfrom
durango:describe-schema
Aug 9, 2013
Merged

Default schemas should now be utilized when describing tables (this real...#812
durango merged 1 commit intosequelize:masterfrom
durango:describe-schema

Conversation

@durango
Copy link
Copy Markdown
Member

@durango 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

…eally only affected Postgres users for the most part) and fixed sqlite/mysql having trouble with dropping the correct schemas. Closes sequelize#672
durango added a commit that referenced this pull request Aug 9, 2013
Default schemas should now be utilized when describing tables (this real...
@durango durango merged commit 75fce70 into sequelize:master Aug 9, 2013
@durango durango deleted the describe-schema branch August 9, 2013 11:34
@josdewitte
Copy link
Copy Markdown

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Postgres describeTableQuery does not respect schema barriers

2 participants