-
Notifications
You must be signed in to change notification settings - Fork 697
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
dateLiteral does not work on OracleDB 12c or 19c #1338
Comments
obabichevjb
added a commit
that referenced
this issue
Apr 25, 2024
obabichevjb
added a commit
that referenced
this issue
Apr 25, 2024
obabichevjb
added a commit
that referenced
this issue
Apr 25, 2024
obabichevjb
added a commit
that referenced
this issue
Apr 25, 2024
obabichevjb
added a commit
that referenced
this issue
Apr 25, 2024
obabichevjb
added a commit
that referenced
this issue
Apr 26, 2024
obabichevjb
added a commit
that referenced
this issue
May 3, 2024
) * EXPOSED-353 dateLiteral does not work on OracleDB 12c or 19c #1338
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
dateLiteral
function does not work on OracleDB (and I suspect the other date/datetime literal functions also do not work for the same reason). The following error is generated:here is the relevant subset of the query that was executed
The generated sql for oracle should be something along the lines of:
Current workarounds are a custom dateliteral function like this:
OR not using a date literal and using a bind variable.
Tested on oracle 12c and 19c.
The text was updated successfully, but these errors were encountered: