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 operator does not work in ISQL [CORE1864] #2294

Closed
firebird-automations opened this issue Apr 24, 2008 · 5 comments
Closed

SELECT operator does not work in ISQL [CORE1864] #2294

firebird-automations opened this issue Apr 24, 2008 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

When doing
SELECT * FROM RDB$DATABASE;
nothing is printed. If you try to repeat it, exception is thrown:
Statement failed SQLCODE = -519.

Was reported originally by Paul Beach.

Commits: 9c55c63 d4ffa30

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

An issue was due to integers, placed in character buffer by yValve in wrong format.

In very many places of engine we do place integers in buffer in VAX format. But we never had common function to do it. Therefore - use of wrong for this purpose put_short and put_long. (Reverse function gds__vax_integer() existrs since beginning of FB time, and therefore no problems with backward conversion.)

I've added put_vax_short and put_vax_long and used them in yValve. Now it will be good idea to use them in all other places of our code base.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

Fix Version: 2.1.1 [ 10223 ]

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Cannot be tested

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