-
-
Notifications
You must be signed in to change notification settings - Fork 496
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
Naming strategy with ORACLE #391
Comments
You can create your own Oracle compiler and override the default Identifiers, and use it instead of the default Oracle Compiler public class MyOracleCompiler : OracleCompiler
{
MyOracleCompiler()
{
OpeningIdentifier = "";
ClosingIdentifier = "";
}
} I think this what you need in your case |
Tried what you suggested. But I am ending up with the following error:
|
Oops, I think overriding the WrapValue method would help in this case. |
Yes I did it and encountered another issue. Not sure if it's related to the SQLKata. In lots of places I got the following error:
|
I don't think it's related, could you share reproducible steps so we can investigate more |
I fixed the issue by converting decimal and int64 into the int32 in my AliasToBeanResultTransformer. Thanks guys I love SQLKata so much. 🥇 Feel free to close the ticket. |
Happy to hear that!, I will close it for now. |
SQLKata 2.2.0
Oracle 18xe
Compiler only with no execution.
I have an issue.
Having names in my app like "snake_case" the SQLKata creates the following query:
select "my_column" from "USER1"."snake_case"
which causes the sql error "table or view not found".
The right solution is to have a query without quotes like:
select my_column from USER1.snake_case
.Along with sqlkata I am using NHibernate with ImprovedNamingStrategy. NHibernate is working fine with those names and produces the queries with no quotes (eg. running QueryOver).
Also my app is using SQLServer and Postgres. Both of them are working with no issues.
Is it possible to tell SQLKata to not wrap names into quotes? Or maybe there is another solution for that. Thanks for any help.
The text was updated successfully, but these errors were encountered: