nextcloud-server.git - Nextcloud server, a safe home for all your data: https://github.com/nextcloud/server

	Commit message (Collapse)	Author	Age	Files	Lines
*	feat(db): add mapping for lock wait timeout	Daniel Kesselberg	2024-05-29	1	-0/+4
\| \| \| \|	Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
*	chore: Add SPDX header	Andy Scherzinger	2024-05-24	1	-20/+2
\| \| \| \|	Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
*	fix: Check for wrapped retriable exceptions	Julius Härtl	2023-05-02	1	-0/+5
\| \| \| \|	Signed-off-by: Julius Härtl <jus@bitgrid.net>
*	composer run cs:fix	Côme Chilliet	2023-01-20	1	-1/+0
\| \| \| \|	Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
*	Update php licenses	John Molakvoæ (skjnldsv)	2021-06-04	1	-5/+6
\| \| \| \|	Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
*	Check for generic errors at last.	Daniel Kesselberg	2021-02-02	1	-13/+13
\| \| \| \|	Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
*	Add our own DB exception abstraction	Christoph Wurst	2021-01-12	1	-0/+136
	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>