Skip to content
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

Closed
firebird-automations opened this issue Mar 18, 2019 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

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.

@firebird-automations
Copy link
Collaborator Author

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?)

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Not reproduced:
#⁠ ./isql employee
Database: employee, User: SYSDBA
SQL> SELECT CURRENT_TIME FROM RDB$DATABASE;

                              CURRENT\_TIME 

==============================================
16:46:18.0000 W-SU

SQL>

What client application did you use?

@firebird-automations
Copy link
Collaborator Author

Commented by: Rudi Feijó (rudi.feijo_multidadosti.com.br)

Ibexpert 2019 .1.15.1

@firebird-automations
Copy link
Collaborator Author

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
In version 4.0, CURRENT_TIME and CURRENT_TIMESTAMP now return TIME WITH TIME ZONE and
TIMESTAMP WITH TIME ZONE, with the time zone set by the session time zone

I see on isql with returns the timestamp with the timezone, ibexpert probably not ready for this

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

One using old client\application could use

SET TIME ZONE BIND LEGACY

to work with old datatypes (with no time zone)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant