We use cookies on our website to improve the performance and content of the site. The cookies enable us to provide a more individual user experience and social media channels.
The Decidim community is called Metadecidim, and it is made up of people and organizations that use the software and want to help improve it.
It's open to anyone who wants to participate 😉
This incidence has been solved. Closed via #4979(External link).
Thank you for contributing!
You need to enable all cookies in order to see this content.
Change cookie settingsWe use cookies to ensure the basic functionalities of the website and to enhance your online experience. You can choose for each category to opt-in/out whenever you want.
These cookies are essential for the proper functioning of my website. Without these cookies, the website would not work properly.
These cookies allow the website to remember the choices you have made in the past
Analytics cookies are cookies that track how users navigate and interact with a website. The information collected is used to help the website owner improve the website.
These cookies collect information about how you use the website, which pages you visited and which links you clicked on.
The piece of text below is a shortened, hashed representation of this content. It is useful to ensure the content has not been tampered with, as a single modification would result in a totally different value.
b5bb727d4251625b0af6c6ffe875942b2863095605d56d3bcc784f3d32175dfe
{"body":{"en":"We have an application running Decidim 0.16.0, the task bundle exec rake decidim:metrics:one[\"results\"] generates the following error:\r\n\r\nActiveRecord::StatementInvalid: PG::GroupingError: ERROR: column \"decidim_accountability_results.id\" must appear in the GROUP BY clause or be used in an aggregate function\r\nLINE 1: ...ipatory_space_id\", decidim_components.id ORDER BY \"decidim_a...\r\n\r\nI've been unable to replicate this in the development_app (there it does not happen). The closest I've get is pointing our application and the development_app both to a cloned Decidim repo on 0.16 and comparing the generated SQL queries (they differ in some points).\r\n\r\nHere I've pasted both queries:\r\n\r\nhttps://gist.github.com/amiedes/8318f5728da87ab5b7bbf223fe0d0220\r\n\r\nI suspect of the extra ORDER BY \"decidim_accountability_results\".\"id\" ASC present in the erroneous query, but I can't guess where it comes from."},"title":{"en":"Broken metrics task: results (wrong SQL query)"}}
This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online(External link) and copy-paste the source data.
Share