Skip to content
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

Cannot do Aggregates in 1.2.0 #39

Closed
ejektaflex opened this issue Sep 11, 2022 · 6 comments
Closed

Cannot do Aggregates in 1.2.0 #39

ejektaflex opened this issue Sep 11, 2022 · 6 comments
Labels
Milestone

Comments

@ejektaflex
Copy link

Attempting an aggregate results in an error. here is the result of my adding a new column to a group for a simple sum:

image

@eirikbakke
Copy link
Contributor

Which database type is this? MySQL, MariaDB, PostgresSQL, Microsoft SQL Server, Oracle, or SQLite?

@eirikbakke
Copy link
Contributor

Also, what is the data type of the column you are trying to SUM?

@eirikbakke
Copy link
Contributor

You can find the database's data type for each column by clicking the small icon in the top right-hand corner of the "Fields" sidebar, then selecting "Backend Type Name" and clicking OK. See the screenshot below.

Backend type

I remember you were using Oracle before, but I tried and didn't get the error when doing a SUM on a regular NUMBER column.

@ejektaflex
Copy link
Author

Oh, this is using an SQLite file. I know it's a bit untested (or, at least, it used to be) and I forgot about that.

I have several records grouped together by a person's name, and I'm adding a new SUM(price) for each person to get a total price of items purchased by each person. As such, the person's name has no backend value but it would be a TEXT. The prices are each a NUMERIC.

@eirikbakke
Copy link
Contributor

Ah, great, now I managed to reproduce it, and fix it. I'll let you know when a new release is out.

Eventually I'll do more work on the SQLite dialect, and get the integration test suite passing on it. Once that is done, there should be fewer surprises.

@eirikbakke eirikbakke added this to the 1.2.1 milestone Sep 11, 2022
@eirikbakke
Copy link
Contributor

There's a new Ultorg release up now, at the old download link, which fixes this bug.

Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants