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
Improve JDBC escape function implementation for CONVERT [JDBC294] #340
Comments
Modified by: @mrotteveelFix Version: Jaybird 2.3 [ 10440 ] description: The current JDBC function escape CONVERT implementation does not support the conversion specified in JDBC 4.1 (which have a SQL_ prefix), because it simply maps it "CAST({0} AS {1})". This also doesn't work for conversions which require a length (CHAR/VARCHAR) and precision (NUMERIC/DECIMAL), as the CONVERT specification (see ODBC documentation: http://msdn.microsoft.com/en-us/library/windows/desktop/ms715381%28v=vs.85%29.aspx ), does not include length or precision. |
Commented by: @mrotteveel Implemented |
Commented by: @mrotteveel DatabaseMetaData.supportsConvert() and DatabaseMetaData.supportsConvert(int, int) need to be implemented as well. |
Commented by: @mrotteveel Implemented supportsConvert |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @mrotteveel
The current JDBC function escape CONVERT implementation does not support the conversion specified in JDBC 4.1 (which have a SQL_ prefix), because it simply maps it "CAST({0} AS {1})".
This also doesn't work for conversions which require a length (CHAR/VARCHAR) and precision (NUMERIC/DECIMAL), as the CONVERT specification (see ODBC documentation: http://msdn.microsoft.com/en-us/library/windows/desktop/ms715381%28v=vs.85%29.aspx ), does not include length or precision.
Commits: 3c4c184 ccd5fc3
The text was updated successfully, but these errors were encountered: