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
Sorting is allowed for blobs [CORE859] #1249
Comments
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 [ 10041 ] |
Commented by: @pcisar Fix confirmed for 2.1 Alpha 1. Test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @pcisar Reopened to update ticket information. |
Commented by: @dyemanov Restored the legacy behavior until we're able to implement DISTINCT for blobs properly. |
Modified by: @dyemanovFix Version: 2.1 Alpha 1 [ 10150 ] => |
Modified by: @pcisarWorkflow: jira [ 11082 ] => Firebird [ 14448 ] |
Modified by: @dyemanovWiki Page: http://wiki.firebirdsql.org/wiki/index.php?page=Monitoring+tables |
Modified by: @dyemanovWiki Page: http://wiki.firebirdsql.org/wiki/index.php?page=Monitoring+tables => |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] => |
Submitted by: @dyemanov
Relate to QA71
Is duplicated by CORE3253
Is duplicated by CORE3252
The engine allows blobs and arrays to be sorted on. Both GROUP BY and ORDER BY on blobs can prepared successfully. All versions (except v2.1) throw a runtime error for GROUP BY due to inability to convert from a blob. ORDER BY [a kind of] works in all versions.
As it produces wrong or undesirable results, cannot be implemented properly due to the sorter restrictions and makes very little sense in practice, I'm going to reject this on the prepare stage.
Commits: b32234e fec2f3e a05bc8f 653dfe8
The text was updated successfully, but these errors were encountered: