By default, the transactions are IBASE_WAIT, so it waits until the record is no longer edited. You have to start a transaction with the IBASE_NOWAIT option to get an immediate response in a deadlock situation.
One example is a php application waiting for desktop app (administration tool) to finish the transaction
When I try to update a record that’s edited in a desktop app or IBexpert, and there is a deadlock, ibase_execute just hangs, does not return any value nor raises an exception.
Well now i noticed that there is a contest so here Firebird is mentioned and enters in the top 5 databases on Linux (Thanks to the Linux Journal readers)
I’m a webmaster amongst other things for a significant web hosting provider.
I wanted to share some code and tricks I come across to pretend I’m knowledgeable, remember to not forget what I’ve learned and because I’m a little jealous of my colleague’s awesome blog.
Norman Dunbar is working in a new documentation describing some of the Firebird internals aspects, like the database file structure, compression used on records, etc.
The document is not finished, but already contains lots of good information.
Thomas Steinmaurer posted in his blog a video showing the differences between Firebird 2.5 SS and CS regarding the use of multiple cores. Watch it now.