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
No integer division possible in dialect 1 [CORE5565] #5832
Comments
Commented by: @mrotteveel Exactly which build did you use? |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: Arkadiusz Wolanski (knuut21) It's 4.0.0.665-0 64 Bit, build 4.0.0.550 work's fine. |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Cannot Reproduce [ 5 ] |
Commented by: Arkadiusz Wolanski (knuut21) Did you try it with a database dialect 1? |
Commented by: @AlexPeshkoff I can reproduce it with current master: # ./isql -sql 1 employee WARNING: This database speaks SQL dialect 3 but Client SQL dialect was set to 1 . |
Modified by: @AlexPeshkoffstatus: Resolved [ 5 ] => Reopened [ 4 ] resolution: Cannot Reproduce [ 5 ] => |
Modified by: @AlexPeshkoffsummary: No in Division possible in dialect 1 => No integer division possible in dialect 1 |
Modified by: @AlexPeshkoffstatus: Reopened [ 4 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Alpha 1 [ 10731 ] |
Commented by: @AlexPeshkoff Arkadiusz, regarding bugs in unreleased versions it's better to use fb-devel instead tracker. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Arkadiusz Wolanski (knuut21)
Following statement:
select d.rdb$relation_id / 1
from rdb$database d
causes following exception:
Unsuccessful execution caused by a system error that precludes successful execution of subsequent statements.
Dynamic SQL Error.
expression evaluation not supported.
Division in dialect 1 must be between numeric data types.
Commits: 665975a
The text was updated successfully, but these errors were encountered: