Hi Noel,
Thanks for the quick turnaround. I'll try it out when the next
release comes out.
Gili
On 18/06/2013 2:54 AM, Noel Grandin wrote:
Done.
Except that I could not make it work for the main primary key on a
table because it would mean removing an optimisation (PageDataIndex
line 98)
On 2013-06-16 18:27, Gili wrote:
Looking at PageBtree.java:121, doesn't H2 have sufficient information
(from SearchRow on line 116) to indicate what key/value pairs causes
the unique constraint? Right now we're only told of the column names
but not what values caused a conflict. Can this be improved?
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
