Olaoluwa Osuntokun 329fcc6498 kvdb+sqldb: update SQL error parsing to account for non wrapped errs ...

Some sub-systems like btcwallet will return an error from the database,
but they won't properly wrap it. As a result, we were unable to actually
catch the serialization errors in the first place. To work around this,
we'll now attempt to parse the error string directly.

2024-04-11 15:04:03 +02:00

..

db_conn_set.go

…

db.go

kvdb+sqldb: use the same tx retry helper

2024-04-11 15:04:02 +02:00

log.go

…

no_sql.go

kvdb: add sqlite

2023-01-23 09:14:08 +02:00

readwrite_bucket.go

kvdb: add sqlite

2023-01-23 09:14:08 +02:00

readwrite_cursor.go

kvdb: add sqlite

2023-01-23 09:14:08 +02:00

readwrite_tx.go

multi: ensure link is always torn down due to db failures, add exponential back off for sql-kvdb failures (#7927)

2023-08-30 16:48:00 -07:00

schema.go

kvdb: add sqlite

2023-01-23 09:14:08 +02:00

sqlerrors_no_postgres.go

kvdb/sqlbase: use positive+negative build tags for new sql error parsing

2023-09-11 20:35:01 -07:00

sqlerrors_no_sqlite.go

kvdb/sqlbase: use positive+negative build tags for new sql error parsing

2023-09-11 20:35:01 -07:00

sqlerrors_postgres.go

kvdb+sqldb: update SQL error parsing to account for non wrapped errs

2024-04-11 15:04:03 +02:00

sqlerrors_sqlite.go

kvdb+sqldb: update SQL error parsing to account for non wrapped errs

2024-04-11 15:04:03 +02:00

sqlerrors.go

kvdb/sqlbase: use positive+negative build tags for new sql error parsing

2023-09-11 20:35:01 -07:00