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

substring from timestamp - unexpected result [CORE2756] #3150

Closed
firebird-automations opened this issue Nov 17, 2009 · 19 comments
Closed

substring from timestamp - unexpected result [CORE2756] #3150

firebird-automations opened this issue Nov 17, 2009 · 19 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Alex Bekhtin (afgm)

FB 2.1
select current_timestamp || '' from rdb$database
2009-11-17 10:55:26.3770

select substring(current_timestamp from 1 for 25) from rdb$database
2009-11-17 10:55:50.5010

FB 2.5
select current_timestamp || '' from rdb$database
2009-11-17 10:56:22.8760

select substring(current_timestamp from 1 for 25) from rdb$database
17-NOV-2009 10:56:41.0790 -- NOV (!)

Commits: e53f869

====== Test Details ======

Test uses SIMILAR TO in order to check format of output.
If it will fail in the future than it can be due to some bugs in SIMILAR TO algorithm.
See CORE2006 and list of tickets related to SIMILAR TO there.

@firebird-automations
Copy link
Collaborator Author

Modified by: Claudio Valderrama C. (robocop)

Version: 3.0 Initial [ 10301 ]

Version: 2.5 RC1 [ 10362 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: Claudio Valderrama C. (robocop)

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

This seems to be already fixed by Alex in a commit that fixed other thing.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC3 [ 10381 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Milan Babuskov (babuskov)

I can confirm that bug still exists in final 2.5 release: LI-V2.5.0.26074 Firebird 2.5

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

Re-opened at Milan's request

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

status: Resolved [ 5 ] => Reopened [ 4 ]

resolution: Fixed [ 1 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

environment: Firebird-2.5.0.25784-0_Win32
XP SP2, Win7

=>

Firebird-2.5.0.25784-0_Win32
XP SP2, Win7, Linux

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Version: 2.5.0 [ 10221 ]

Fix Version: 2.5.1 [ 10333 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Brenden Walker (braindead)

This appears to be fixed (for me) in Windows 7 64 bit running FB 2.5.0 26074, 32-bit.

SQL> select current_timestamp || '' from rdb$database;

CONCATENATION

2010-12-27 14:17:32.6770

SQL> select substring(current_timestamp from 1 for 25) from rdb$database;

SUBSTRING

27-DEC-2010 14:17:44.5470

@firebird-automations
Copy link
Collaborator Author

Commented by: Anderson Freitas Alves (builder_rs)

Error not found in:

- LI-V2.5.0.26076 Firebird 2.5 SuperClassic
- LI-V2.5.1.26160 Firebird 2.5 SuperClassic

Tested in server CentOS Linux 5.5 64 bits, with FlameRobin 0.9.3.2077 Unicode running in Windows XP.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Alex, could you please re-test whether the issue really exists in v2.5.0 26074 and, if so, whether it had disappeared in the subsequent builds?

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Dmitry, it see it reproduced in both 2.5.0 26074 & 2.5.1.26166, i.e. it has not disappeared. What is our release schedule for 2.5.1?

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

February, I guess. So we still have some time for bug fixing.

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Issue was noticed by Claudio in HEAD a year ago and fixed by me without ticket on the tracker - it seemed that this is head-specific thing. Now I've backported this fix to 2.5, i.e. everything should be OK in 2.5.1.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Reopened [ 4 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Done successfully

Test Details: See also test for CORE2006

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

Test Details: See also test for CORE2006 => Test uses SIMILAR TO in order to check format of output.
If it will fail in the future than it can be due to some bugs in SIMILAR TO algorithm.
See CORE2006 and list of tickets related to SIMILAR TO there.

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