Repository navigation
MySQL mode does not respect IGNORECASE/CASE_INSENSITIVE_IDENTIFIERS in 'on duplicate key update' part (H2 2.3.232) #4238
Description
The following code does not work in MySQL mode with IGNORECASE=TRUE;CASE_INSENSITIVE_IDENTIFIERS=TRUE:
create table foo (
id bigint not null auto_increment,
bar varchar2 not null,
primary key (id),
unique (bar)
);
insert into FOO (bar) values ('bar'); -- works
select bar from FOO; -- works
insert into FOO (bar) values ('bar') on duplicate key update foo.id = foo.id; -- works
insert into FOO (bar) values ('bar') on duplicate key update FOO.id = FOO.id; -- error: [Table "FOO" not found; SQL statement:]
Activity
katzyn commentedon Jun 17, 2025
You should always use
DATABASE_TO_LOWER=TRUEtogether with MySQL compatibility mode.CASE_INSENSITIVE_IDENTIFIERS=TRUEis only needed when your application uses standard quoted identifiers ("FOO") in incorrect way, but MySQL doesn't use this type of identifiers unlessANSI_QUOTESare enabled, so usually you don't need this setting at all.Anyway, it somehow breaks this weird compatibility syntax, so there is a bug.