8 Commits (2bc77a3c5aff352cdc19aa683bbb36da2ff20b01)

Author	SHA1	Message	Date
Robin Appelman	f3bd4a79d9	feat: log query for dbal exceptions ... Signed-off-by: Robin Appelman <robin@icewind.nl>	10 months ago
Daniel Kesselberg	3fb0aa40cd	feat(db): add mapping for lock wait timeout ... Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>	2 years ago
Andy Scherzinger	dae7c159f7	chore: Add SPDX header ... Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>	2 years ago
Julius Härtl	3bdd770129	fix: Check for wrapped retriable exceptions ... Signed-off-by: Julius Härtl <jus@bitgrid.net>	3 years ago
Côme Chilliet	f5c361cf44	composer run cs:fix ... Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>	3 years ago
John Molakvoæ (skjnldsv)	215aef3cbd	Update php licenses ... Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>	5 years ago
Daniel Kesselberg	fe378200fa	Check for generic errors at last. ... Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>	5 years ago
Christoph Wurst	2c9cdc1cdb	Add our own DB exception abstraction ... Right now our API exports the Doctrine/dbal exception. As we've seen with the dbal 3 upgrade, the leakage of 3rdparty types is problematic as a dependency update means lots of work in apps, due to the direct dependency of what Nextcloud ships. This breaks this dependency so that apps only need to depend on our public API. That API can then be vendor (db lib) agnostic and we can work around future deprecations/removals in dbal more easily. Right now the type of exception thrown is transported as "reason". For the more popular types of errors we can extend the new exception class and allow apps to catch specific errors only. Right now they have to catch-check-rethrow. This is not ideal, but better than the dependnecy on dbal. Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>	5 years ago