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
Some of the JDBC function escapes support optional parameters (most of which modify the behaviour of the function). The current parser does not support optional parameter.
Examples of functions are:
CHAR_LENGTH(string[,CHARACTERS|OCTETS})
CHARACTER_LENGTH(string[,CHARACTERS|OCTETS})
LENGTH(string[,CHARACTERS|OCTETS})
POSITION(substring IN string[,CHARACTERS|OCTETS])
SUBSTRING(string, start, length[, CHARACTERS|OCTETS})
LOCATE(string1, string2[, start])
In the case of CHAR_LENGTH AND CHARACTER_LENGTH the current implementation simply ignores the last parameter if specified, this is incorrect for OCTETS. In the case of LOCATE we currently only support the version that includes the optional parameter.
Submitted by: @mrotteveel
Some of the JDBC function escapes support optional parameters (most of which modify the behaviour of the function). The current parser does not support optional parameter.
Examples of functions are:
CHAR_LENGTH(string[,CHARACTERS|OCTETS})
CHARACTER_LENGTH(string[,CHARACTERS|OCTETS})
LENGTH(string[,CHARACTERS|OCTETS})
POSITION(substring IN string[,CHARACTERS|OCTETS])
SUBSTRING(string, start, length[, CHARACTERS|OCTETS})
LOCATE(string1, string2[, start])
In the case of CHAR_LENGTH AND CHARACTER_LENGTH the current implementation simply ignores the last parameter if specified, this is incorrect for OCTETS. In the case of LOCATE we currently only support the version that includes the optional parameter.
Commits: ccd5fc3
The text was updated successfully, but these errors were encountered: