Grouping is messed up when calling un-grouped query using same tables as previous query #43

Closed
opened 2019-11-25 23:28:44 +00:00 by jamie · 4 comments
jamie commented 2019-11-25 23:28:44 +00:00 (Migrated from git.hazaar.io)

This only happens when calling a grouped query, then after that calling an ungrouped query that uses tables that were in the grouped query. The result being the ungrouped query results are returned grouped because the group data is not flushed out.

Grouped query results is a new feature so this isn't affecting much yet.

This only happens when calling a grouped query, then after that calling an ungrouped query that uses tables that were in the grouped query. The result being the ungrouped query results are returned grouped because the group data is not flushed out. Grouped query results is a new feature so this isn't affecting much yet.
jamie commented 2019-11-25 23:28:47 +00:00 (Migrated from git.hazaar.io)

created merge request !17 to address this issue

created merge request !17 to address this issue
jamie commented 2019-11-25 23:28:47 +00:00 (Migrated from git.hazaar.io)

mentioned in merge request !17

mentioned in merge request !17
jamie commented 2019-11-26 00:30:59 +00:00 (Migrated from git.hazaar.io)

closed via merge request !17

closed via merge request !17
jamie commented 2019-11-26 00:30:59 +00:00 (Migrated from git.hazaar.io)

mentioned in commit bbb884fdae

mentioned in commit bbb884fdaee079983784577bd01025afba00a76a
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-dbi#43
No description provided.