New answers tagged constraint
I ended up here with very same error, which was occuring rarely, and was hard to track, because I was loking for it not where I should. Fault was JS repetition which was doing the POST to the server twice! So sometimes it is worth to have a look not only on your django (or any other web framework) views and forms but also what happens on very front side.
Because the value is incremented outside the scope of the transaction. This is the way you want it to work, so that separate transactions can happily insert rows or roll back without waiting for each other. If you care about gaps or want different behavior, stop using the built in and roll your own...
Please stop using INFORMATION_SCHEMA and deprecated backward compatibility views like sysobjects. This is just another in the long list of things that INFORMATION_SCHEMA is missing in order to provide a complete picture of your metadata. See this post for a more exhaustive list: The case against INFORMATION_SCHEMA views To find the name of the default ...
create before insert/ before update trigger/s on Friendship Members table table Friendships has nothing to do with the relation so you probably want so leave it aside for now. the trigger should check id X can not have relation with id X if id X is in relation with id Y than do not create relation between id Y and id X triggers
Top 50 recent answers are included