Files
iTop/core
Pierre Goiffon 0ffa2850ea Deadlock log : log inside a dedicated log file instead of creating an EventIssue object (#139)
First log implementation (75730ee) was creating EventIssue objects, and was rollbacking transaction if it exists

The new one has some benefits :

* always log one line by default in log/error.log, but details must be activated though config (channels `Deadlock-WaitTimeout` and `Deadlock-Found`)
* detailed logs are in a dedicated file (log/deadlock.log) : 
  - easier for our clients to get and share
  - has rotation by default
  - looking at the file size is a direct way to know if error happened
  - more compliant to industry standards !
* the transaction stays untouched, so that the consumer can do whatever it prefers
2020-05-14 17:49:05 +02:00
..
2019-01-24 18:07:50 +01:00
2020-05-06 10:29:47 +02:00
2017-05-05 15:08:49 +00:00
2019-11-28 17:03:31 +01:00
2018-07-13 08:34:47 +00:00
2019-08-13 17:25:04 +02:00