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

Inconsistency of formatting double precision values between linux and windows [CORE5665] #5931

Open
firebird-automations opened this issue Nov 20, 2017 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @artyom-smirnov

Also probably inconsistency of formatting values in range -1 < 0 < 1. Padding zeros not always rendered right.

set list;
select char_length(cast(cast(0 as double precision) as varchar(20))),
char_length(cast(cast(0.1 as double precision) as varchar(20))),
char_length(cast(cast(1 as double precision) as varchar(20))),
char_length(cast(cast(1.1 as double precision) as varchar(20))) from rdb$database;

on linux result is:
CHAR_LENGTH 17
CHAR_LENGTH 18
CHAR_LENGTH 17
CHAR_LENGTH 17

on windows result is:
CHAR_LENGTH 18
CHAR_LENGTH 18
CHAR_LENGTH 17
CHAR_LENGTH 17

@firebird-automations
Copy link
Collaborator Author

Modified by: @artyom-smirnov

Component: Engine [ 10000 ]

Component: ISQL [ 10003 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Only way to avoid it would be to hand-write CRT-agnostic conversion function.

Not sure it's the way to go.

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