Hi, It looks like using PublishedEvent with a table IsisPublishedEvent with engine InnoDB gives some trouble.
I'm persisting 2 objects of the same entity with @Published-annotation in one transaction. Isis tries to insert 2 corresponding rows in an EMPTY IsisPublishedEvent-table. The first with sequence 0, the second with sequence 1. This gives a duplicate key exception for the primary key, I think because MySQL inserts the first entry with a sequence = 1 (0 is not allowed in InnoDB). The second insert will fail because sequence 1 already exists. The same action will succeed when going back to the objectform and doing the same again :-$ (still with an empty table) This gives exactly the same insert-statements (with sequence 0 and 1) but this time all goes well. Entries will be inserted with sequence 1 and 2. I can work around this by inserting a row in IsisPublishedEvent with sequence 1. Is this a bug or am I doing something wrong? Erik
