| Re: How to deal with multiple inserts in ADD1 pattern [message #5885 is a reply to message #5884] |
Mon, 19 September 2016 15:07   |
kong
Messages: 90
Registered: December 2011
|
Member |
|
|
My first post is about using the auto-increment, which will just produce multiple duplicated records with incremented primary key as expected.
In my second post I tried to avoid getting these duplicated records with just incremented primary keys by changing the table to use varchar(13) as primary key instead of auto-increment. The hope was that then only one record should be generated and subsequent inserts should have resulted in "duplicate error", just as you said. It is in my second post (using unique key ABC123) that I discovered the bug that shows the system does not always result in "duplicate error", but will sometimes throw a fatal error by MySQL crashing the application. I am using only standard transaction pattern components without any customization, and have not made any changes or customization in locking strategy between the components.
The content of this topic has digressed from the title. So, I have raised a new topic here: http:// radicore.org/fud/index.php?t=msg&goto=5886&#msg_5886
[Updated on: Tue, 20 September 2016 01:35] Report message to a moderator |
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
