aboutsummaryrefslogtreecommitdiff
path: root/sqlite
diff options
context:
space:
mode:
authorfusion32 <marcopuzziello@gmail.com>2025-10-18 03:40:40 -0300
committerfusion32 <marcopuzziello@gmail.com>2025-10-18 03:40:40 -0300
commitebf536a7910f6e8d5bff569d2d717287ad3ba716 (patch)
tree3033c280b90ddcd1ebe067d840cce94eb8c3566a /sqlite
parent601ce32ee8d0cee32b66c87b0bfefa7424a5b8c8 (diff)
downloadquerymanager-ebf536a7910f6e8d5bff569d2d717287ad3ba716.tar.gz
querymanager-ebf536a7910f6e8d5bff569d2d717287ad3ba716.zip
properly handle NULL values with postgres result helpers
Diffstat (limited to 'sqlite')
-rw-r--r--sqlite/README.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/sqlite/README.txt b/sqlite/README.txt
index 8ef89f5..9924007 100644
--- a/sqlite/README.txt
+++ b/sqlite/README.txt
@@ -7,5 +7,6 @@ files will be executed exactly ONCE. If multiple patches are pending at startup,
they're executed in alphabetical order.
As for statement restrictions, the only thing prohibited is the presence of
transaction statements "BEGIN", "ROLLBACK", and "COMMIT". This is because all
-patches will be bundled into the same transaction, to ensure atomicity.
+patches will be bundled into the same transaction, to ensure atomicity, and
+there can't be nested transactions.