Hi, > What my distributed key does is that it guards the the uniqueness of the > distributed key. So statement insert into b values(13) would throw a unique > key violation exception.
You can do that with triggers. Before an insert, check if the value exists in another table. > small change set that I did that would allow trigger to set the generated key So, as far as I understand, this is not needed to implement the above feature. 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.
