-
Notifications
You must be signed in to change notification settings - Fork 36
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
Table aggregation limit and suffix settings not respected #1144
Comments
Specify 7 currently ignores the the count and ending settings of aggregators. This applies to queries as well. |
Because Specify 7 does all the formatting and aggregation at the database level, tt would be best to figure out how to express the logic in SQL. MariaDB supports a limit clause in the GROUP_CONCAT function which fits the bill nicely:
To support it in MySQL it would probably be necessary to use SUBSTRING_INDEX on the separator after suppressing any occurrence of the separator in the values using REPLACE. I'm thinking it wouldn't be too hard to add either of these approaches, but the MariaDB one is better. It might be possible to check if the server is MySQL or MariaDB and generate the corresponding SQL. The relevant code is at specify7/specifyweb/stored_queries/format.py Line 168 in 7b3cbc9
specify7/specifyweb/stored_queries/group_concat.py Lines 12 to 26 in 7b3cbc9
|
|
#2796 adds front-end support for this. Back-end support is still pending |
Can recreate in edge (7.9.6) |
Describe the bug
The schema configuration's customized aggregation does not effect how the report runner works.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
In Specify 6, the schema configuration is respected when running a report. In Specify 7, reports ignore this configuration but should do the same.
Screenshots
![D4bss8pAhj](https://user-images.githubusercontent.com/37256050/150010234-25a79db9-ab0b-4ba6-8275-0a75e8e3d00f.png)
Desktop (please complete the following information):
Reported By
Grant on behalf of LSUMZ
The text was updated successfully, but these errors were encountered: