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
Make quoting identifiers optional. #1761
Comments
Any particular reason why this would be useful feature? |
yes, specifically for oracle. In my case with oracle |
@atiertant any ideas if this is somehow possible with oracle or should people just write their code case-sensitive way? |
@elhigu we should implement a fromRaw method |
@atiertant I have no idea what you mean by I was trying to ask if this is a good idea to support disabling identifier quoting on oracle or if there are better ways to get around the problem (e.g. some other global setting in database)? Would disabling quotes introduce any other potential problems? |
@elhigu like |
Would be great, would eliminate my problem with table-names including dots. They need to be escaped with quotes and this isn't possible with knex right now. |
I'm not sure if |
@ravshansbox I agree that We may continue this discussion if someone seriously considers implementing / testing / documenting this feature. |
@elhigu @ravshansbox i'm not sure using unquoted column/table name is the best way too... but |
@atiertant I'll add it as a separate issue, it is just a missing API which I didn't even knew didn't exist |
This a problem for Oracle users. It would be nice to optionally remove the quotes or force the case to upper (as Oracle does for table names). If not, knex users who have Oracle need to change all of their scripts / queries to use quotes and if they use third party software (for example for reporting) they'll need to contact those companies to ask them to add quotes. Is there anyone working on this in knex? |
@jtal I don't believe that anyone is working on this. I fail to see the point how 3rd party software generated queries would require changes? One can run queries like that already by using |
Hi, is there some advance to this issue? Thanks. |
In next release you will be able to create custom quoting functionality #2084 |
Thanks bro! It works for me. I basically have used: .select() and query was wrote as: select * from myschema.mytable. before it, i was using: and query was: select * from "myschema"."mytable" and it was throwing an error. Now it works. Thank you!!! |
No description provided.
The text was updated successfully, but these errors were encountered: