Skip to content
Snippets Groups Projects
  1. Mar 30, 2021
  2. Mar 22, 2021
  3. Mar 03, 2021
  4. Feb 02, 2021
  5. Jan 12, 2021
    • Christoph Wurst's avatar
      Add our own DB exception abstraction · 2c9cdc1c
      Christoph Wurst authored
      
      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: default avatarChristoph Wurst <christoph@winzerhof-wurst.at>
      2c9cdc1c
  6. Jan 11, 2021
  7. Jan 08, 2021
  8. Dec 30, 2020
  9. Dec 16, 2020
  10. Dec 14, 2020
  11. Dec 09, 2020
  12. Dec 07, 2020
  13. Dec 02, 2020
  14. Nov 16, 2020
  15. Nov 11, 2020
  16. Nov 10, 2020
  17. Nov 07, 2020
  18. Nov 06, 2020
  19. Nov 03, 2020
  20. Oct 30, 2020
  21. Oct 29, 2020
  22. Oct 05, 2020
  23. Oct 03, 2020
  24. Oct 02, 2020
  25. Sep 25, 2020
  26. Sep 17, 2020
Loading