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

PostgresQueryRunner.hasColumn throw error #202

Closed
mingyang91 opened this issue Jan 14, 2017 · 1 comment
Closed

PostgresQueryRunner.hasColumn throw error #202

mingyang91 opened this issue Jan 14, 2017 · 1 comment
Labels

Comments

@mingyang91
Copy link
Contributor

Error log

[2017-01-14 16:21:44.727] [ERROR] DB - query failed: SELECT * FROM information_schema.tables WHERE table_catalog = 'ebdb' AND table_schema = 'public' AND table_name = 'candidate' AND column_name = 'phone'
[2017-01-14 16:21:44.727] [ERROR] DB - error during executing query:error: column "column_name" does not exist
[2017-01-14 16:21:44.730] [DEBUG] DB - executing query: ROLLBACK
[2017-01-14 16:21:44.764] [ERROR] DB_Connection - { error: column "column_name" does not exist
    at Connection.parseE (/Users/famer.me/Repository/vein/node_modules/pg/lib/connection.js:554:11)
    at Connection.parseMessage (/Users/famer.me/Repository/vein/node_modules/pg/lib/connection.js:381:17)

I think the sql in the hasColumn is not correct.
information_schema.tables table does not contain column column_name, he should be modified to information_schema.columns.

mingyang91 added a commit to mingyang91/typeorm that referenced this issue Jan 14, 2017
pleerock pushed a commit that referenced this issue Jan 14, 2017
@pleerock
Copy link
Member

Released in 0.0.7-alpha.19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants