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
SELECT CURRENT_TIME FROM RDB$DATABASE returns error (invalid datatype?) [CORE6025] #6275
Comments
Modified by: Rudi Feijó (rudi.feijo_multidadosti.com.br)summary: SELECT CURRENT_TIME FROM RDB$DATABASE crashses (invalid datatype?) => SELECT CURRENT_TIME FROM RDB$DATABASE returns error (invalid datatype?) |
Commented by: @AlexPeshkoff Not reproduced:
============================================== SQL> What client application did you use? |
Commented by: Rudi Feijó (rudi.feijo_multidadosti.com.br) Ibexpert 2019 .1.15.1 |
Commented by: Rudi Feijó (rudi.feijo_multidadosti.com.br) sorry, just read the release notes and realized its intended behaviour Expressions CURRENT_TIME and CURRENT_TIMESTAMP I see on isql with returns the timestamp with the timezone, ibexpert probably not ready for this |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @hvlad One using old client\application could use SET TIME ZONE BIND LEGACY to work with old datatypes (with no time zone) |
Submitted by: Rudi Feijó (rudi.feijo_multidadosti.com.br)
SELECT CURRENT_TIME FROM RDB$DATABASE
or
SELECT CURRENT_TIMESTAMP FROM RDB$DATABASE
returns invalid datatype error.
Tried both in a db restored from fb 3, and a newly created fb 4 one.
The text was updated successfully, but these errors were encountered: