Bug: various int arrays are generated as `types.Int64Array` which leads to out of range errors in tests

[erezrokah]

What version of SQLBoiler are you using (sqlboiler --version)?

SQLBoiler v4.15.0 (Actually I'm using the latest code from master)

What is your database and version (eg. Postgresql 10)

Postgres 15

If this happened at generation time what was the full SQLBoiler command you used to generate your models? (if not applicable leave blank)

sqlboiler psql --wipe --no-hooks --no-auto-timestamps --no-back-referencing

If this happened at runtime what code produced the issue? (if not applicable leave blank)

N/A

What is the output of the command above with the -d flag added to it? (Provided you are comfortable sharing this, it contains a blueprint of your schema)

Please provide a relevant database schema so we can replicate your issue (Provided you are comfortable sharing this)

create table if not exists my_table(
    id serial primary key,
    small_ints smallint[]
);

Further information. What did you do, what did you expect?

Looks like various types of int arrays are always generated as types.Int64Array:

https://github.com/volatiletech/sqlboiler/blob/59e63d54028be0a3b89318577a80fdebd7e351cb/drivers/sqlboiler-psql/driver/psql.go#L918, which means when seeding the values with random data it can overflow the DB type

[kylelmh]

I am facing the same problem.
From the source code, looks like int32 arrays are not checked. I think it would be a matter of adding a []int check before the int64 check and a new IntArray type. But this could cause overflow if the int in question is int64, just not over 32 bits in value yet...

https://github.com/volatiletech/sqlboiler/blob/8c10c060bc36f4f3be00322212e96402b03732b4/types/array.go#L462-L487

I am working around this by manually modifying the generated files to match my schema definition, but this is hard to maintain. Maybe it would be useful to define overrides in the generation process?

[stephenafamo]

PR welcome 🙏🏾