One benefit of H2 is that it is very good at impersonating multiple
databases.  We haven’t seen these errors previously.  What test is this
occurring in?

 I assume by reals you mean a Double is being used?  Why is a numeric not
being used?

On Sun, May 11, 2025 at 8:02 PM Walter Duque de Estrada
<wbdu...@icloud.com.invalid> wrote:

> Team:
> The following error  is related to using H2 for testing
>
> org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing
> DDL "create table common_types (b tinyint not null, bd numeric(19,2) not
> null, bi numeric(19,0) not null, bool boolean not null, cur varchar(3) not
> null, d float(64) not null, f float(64) not null, i integer not null, s
> smallint not null, c timestamp(6) not null, date timestamp(6) not null, id
> bigint generated by default as identity, l bigint not null, version bigint
> not null, ba varbinary(255) not null, loc varchar(255) not null, tz
> varchar(255) not null, url varchar(255) not null, primary key (id))" via
> JDBC [Precision ("64") must be between "1" and "53" inclusive;
>
> There are two paths here:
>
> 1) Remove reals from testing. I do not like this.
> 2) Swap out for postgresql. In the branch I was working I had it working
> with test containers.
>
>
> What does the group think?
>
> Walter Duque de Estrada
>
>
>
>
>
  • H2 error Walter Duque de Estrada
    • Re: H2 error James Daugherty

Reply via email to