You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The schema file was generated by another tool (Atlas), which always backquotes table and column names.
The query file was written by me and does not use backquotes.
This mismatch resulted in a relation "users" does not exist" error. However, when I removed the backquotes, it worked.
As the example above shows, some SQL tools generate backquoted names, while in some cases, developers do not. Ignoring the difference in backquotes could simplify things. Is this possible?
What database engines need to be changed?
SQLite
What programming language backends need to be changed?
Go
The text was updated successfully, but these errors were encountered:
tenkoh
changed the title
Want not to distinguish table names like model and model
Want not to distinguish table names like <code></code>model<code></code> and model
Aug 15, 2024
tenkoh
changed the title
Want not to distinguish table names like <code></code>model<code></code> and model
Want not to distinguish between table names with backquotes and ones without backquotes.
Aug 15, 2024
What do you want to change?
Thank you for an awesome tool!
When I had tried a simple schema and a query for SQLite3, I got
relation "users" does not exist"
error.playground:
https://play.sqlc.dev/p/70a186af745e44d972ae126b78f83a98443a3a70d8bc42462109703baf239ac0
This mismatch resulted in a
relation "users" does not exist"
error. However, when I removed the backquotes, it worked.As the example above shows, some SQL tools generate backquoted names, while in some cases, developers do not. Ignoring the difference in backquotes could simplify things. Is this possible?
What database engines need to be changed?
SQLite
What programming language backends need to be changed?
Go
The text was updated successfully, but these errors were encountered: