[h2] Re: UNIQUE KEY constraint in H2-1.4.199 is not working with H2-2.2.224

Hi Evgenij Ryazanov , Thank you so much for your quick response and the suggestion. When changed the constraint to a standard CONSTRAINT mdrIdProeprtyName UNIQUE(mdr_id, property_name) the error is not shown. Thanks, Balamurali On Friday, February 9, 2024 at 12:46:17 PM UTC+5:30 Evgenij Ry

[h2] Re: UNIQUE KEY constraint in H2-1.4.199 is not working with H2-2.2.224

Hi! Your table definition has non-portable MySQL-specific syntax. If this is not your intention, you should use standard CONSTRAINT mdrIdProeprtyName UNIQUE(mdr_id, property_name) instead. MySQL-specific features are only allowed in MySQL and MariaDB compatibility modes: https://h2database.com

[h2] UNIQUE KEY constraint in H2-1.4.199 is not working with H2-2.2.224

Hi Team, I have a table schema in my H2 DB like below and when I am doing the build with H2DB 1.4.199 the table query is working fine but when using the H2DB 2.2.224 jar and while doing hte build it was giving "Expected NULLS" issue as shown below: Create Table Query: CREATE T