Hi Thomas,
thanks for the quick response, this helped me.
But why a different message occur for other ('normal') cases?
Is it different because the primary key (MYTABLE.ID) instead of the
additional unique constraint (on MYTABLE.NAME) is violated?
Regards,
Peter.
On Jul 13, 8:10 pm, Thomas Mueller <[email protected]>
wrote:
> Hi,
>
> > Unique index or primary key violation: "MYTABLE_DATA ON
> > PUBLIC.MYTABLE(ID, CREATEDAT, ..., ...)"
>
> The problem is that there was a primary key violation. I agree it's a
> weird error message, I will fix that in the next release. However,
> it's definitely a primary key violation. Here is a test case that
> throws a similar exception:
>
> DROP TABLE IF EXISTS TEST;
> CREATE TABLE TEST(ID INT PRIMARY KEY, NAME VARCHAR(255));
> INSERT INTO TEST VALUES(1, 'Hello');
> INSERT INTO TEST VALUES(1, 'World');
> -- Unique index or primary key violation: "TEST_DATA ON PUBLIC.TEST(ID, NAME)"
>
> > Is my database corrupt like suggested
> > here:http://fri13th.com/blog/archives/285
>
> No. This blog article is quite old (2007). There were a lot of changes
> in H2 since then. And this error message is not related to corruption.
>
> Regards,
> Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
