zeripath 716fcfcf72 Make every not exist error unwrappable to a fs.ErrNotExist (#20891) ... A lot of our code is repeatedly testing if individual errors are specific types of Not Exist errors. This is repetitative and unnecesary. `Unwrap() error` provides a common way of labelling an error as a NotExist error and we can/should use this. This PR has chosen to use the common `io/fs` errors e.g. `fs.ErrNotExist` for our errors. This is in some ways not completely correct as these are not filesystem errors but it seems like a reasonable thing to do and would allow us to simplify a lot of our code to `errors.Is(err, fs.ErrNotExist)` instead of `package.IsErr...NotExist(err)` I am open to suggestions to use a different base error - perhaps `models/db.ErrNotExist` if that would be felt to be better. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: delvh <dev.lh@web.de>		2022-10-18 07:50:37 +02:00
..
install
paginator
common.go
consistency.go
context.go
convert.go
engine_test.go
engine.go	Make every not exist error unwrappable to a fs.ErrNotExist (#20891)	2022-10-18 07:50:37 +02:00
error.go	Make every not exist error unwrappable to a fs.ErrNotExist (#20891)	2022-10-18 07:50:37 +02:00
index_test.go	Refactor GetNextResourceIndex to make it work properly with transaction (#21469)	2022-10-16 18:44:16 +08:00
index.go	Refactor GetNextResourceIndex to make it work properly with transaction (#21469)	2022-10-16 18:44:16 +08:00
iterate.go
list_options.go
log.go
main_test.go
name.go	Make every not exist error unwrappable to a fs.ErrNotExist (#20891)	2022-10-18 07:50:37 +02:00
search.go
sequence.go
sql_postgres_with_schema.go