swelham

swelham

We’re in the process of moving our codebase from Postgres to MySQL (using PlanetScale) and we’re noticing a number of our aggregate queries are now trying to calculate using the Decimal<> type, instead of integers.

For example, the following query treats the column types differently depending on which adapter we’re using.

SomeTable
|> select([t], sum(t.int_col_one) - sum(i.int_col_two))
|> Repo.one()

Using Postgres this will subtract two integers.

Using MySQL (using MyXQL) it will attempt to subtract from a decimal.

Error thrown from the query

bad argument in arithmetic expression: Decimal.new("7401") - 7401

:erlang.-(Decimal.new("7401"), 7401)

We have also observed sum and avg aggregates also return decimal types now (all columns are integers) where as previously we would get an integer back when using Postgres.

I haven’t found much info on this so any pointers or solutions would be appreciated.

Showing Posts 1 to 2

sbuttgereit

sbuttgereit

This appears to be documented behavior of the sum and avg aggregates in MySQL:

The SUM() and AVG() functions return a DECIMAL value for exact-value arguments (integer or DECIMAL), and a DOUBLE value for approximate-value arguments (FLOAT or DOUBLE).

Having survived many data migration projects my best advice is that different database vendors do similar things differently: never take for granted that similar operations are in fact the same operation across database products.

LostKobrakai

LostKobrakai

Yeah, even postgres returns a numeric for sum(bigint) -> numeric vs. sum(integer) -> bigint.

I also want to explicitly highlight: this is not ectos doing. Ecto just builds a query for the database to execute and transform any data getting back from the db. It’s not meant to abstract any differences between databases. It just allows you to work with different databases using the same tools.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews