erdbpro 2.4.5 → 2.5.2-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (28) hide show
  1. package/README.md +49 -8
  2. package/dist/assets/{index-DgkcaXbc.js → index-DWOX2re7.js} +332 -332
  3. package/dist/index.html +1 -1
  4. package/dist-server/index.js +94 -94
  5. package/dist-server/node_modules/better-sqlite3/build/Release/.deps/Release/obj.target/better_sqlite3/src/better_sqlite3.o.d.raw +82 -0
  6. package/dist-server/node_modules/better-sqlite3/build/Release/.deps/Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o.d +4 -0
  7. package/dist-server/node_modules/better-sqlite3/build/Release/.deps/Release/sqlite3.a.d +1 -0
  8. package/dist-server/node_modules/better-sqlite3/build/Release/better_sqlite3.node +0 -0
  9. package/dist-server/node_modules/better-sqlite3/build/Release/obj/gen/sqlite3/sqlite3.c +692 -176
  10. package/dist-server/node_modules/better-sqlite3/build/Release/obj/gen/sqlite3/sqlite3.h +17 -5
  11. package/dist-server/node_modules/better-sqlite3/build/Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o +0 -0
  12. package/dist-server/node_modules/better-sqlite3/build/Release/sqlite3.a +0 -0
  13. package/dist-server/node_modules/better-sqlite3/deps/download.sh +1 -1
  14. package/dist-server/node_modules/better-sqlite3/deps/sqlite3/sqlite3.c +692 -176
  15. package/dist-server/node_modules/better-sqlite3/deps/sqlite3/sqlite3.h +17 -5
  16. package/dist-server/node_modules/better-sqlite3/package.json +1 -1
  17. package/dist-server/node_modules/better-sqlite3/src/better_sqlite3.cpp +1 -1
  18. package/dist-server/node_modules/better-sqlite3/src/util/helpers.cpp +1 -1
  19. package/dist-server/node_modules/better-sqlite3/src/util/macros.cpp +8 -1
  20. package/menubar/ERDBProTray.app/Contents/Info.plist +20 -0
  21. package/menubar/ERDBProTray.app/Contents/MacOS/ERDBProTray +0 -0
  22. package/menubar/ERDBProTray.swift +129 -0
  23. package/menubar/erdbpro-tray +0 -0
  24. package/menubar/icon.svg +14 -0
  25. package/menubar/launch.sh +4 -0
  26. package/menubar/tray.sh +59 -0
  27. package/package.json +10 -8
  28. package/src/cli.mjs +197 -28
@@ -146,12 +146,12 @@ extern "C" {
146
146
  ** [sqlite3_libversion_number()], [sqlite3_sourceid()],
147
147
  ** [sqlite_version()] and [sqlite_source_id()].
148
148
  */
149
- #define SQLITE_VERSION "3.53.1"
150
- #define SQLITE_VERSION_NUMBER 3053001
151
- #define SQLITE_SOURCE_ID "2026-05-05 10:34:17 c88b22011a54b4f6fbd149e9f8e4de77658ce58143a1af0e3785e4e6475127e9"
149
+ #define SQLITE_VERSION "3.53.2"
150
+ #define SQLITE_VERSION_NUMBER 3053002
151
+ #define SQLITE_SOURCE_ID "2026-06-03 19:12:13 d6e03d8c777cfa2d35e3b60d8ec3e0187f3e9f99d8e2ee9cac695fd6fcdf1a24"
152
152
  #define SQLITE_SCM_BRANCH "branch-3.53"
153
- #define SQLITE_SCM_TAGS "release version-3.53.1"
154
- #define SQLITE_SCM_DATETIME "2026-05-05T10:34:17.344Z"
153
+ #define SQLITE_SCM_TAGS "release version-3.53.2"
154
+ #define SQLITE_SCM_DATETIME "2026-06-03T19:12:13.350Z"
155
155
 
156
156
  /*
157
157
  ** CAPI3REF: Run-Time Library Version Numbers
@@ -12853,11 +12853,23 @@ SQLITE_API int sqlite3changeset_apply_v3(
12853
12853
  ** database behave as if they were declared with "ON UPDATE NO ACTION ON
12854
12854
  ** DELETE NO ACTION", even if they are actually CASCADE, RESTRICT, SET NULL
12855
12855
  ** or SET DEFAULT.
12856
+ **
12857
+ ** <dt>SQLITE_CHANGESETAPPLY_NOUPDATELOOP <dd>
12858
+ ** Sometimes, a changeset contains two or more update statements such that
12859
+ ** although after applying all updates the database will contain no
12860
+ ** constraint violations, no single update can be applied before the others.
12861
+ ** The simplest example of this is a pair of UPDATEs that have "swapped"
12862
+ ** two column values with a UNIQUE constraint.
12863
+ ** <p>
12864
+ ** Usually, sqlite3changeset_apply() and similar functions work hard to try
12865
+ ** to find a way to apply such a changeset. However, if this flag is set,
12866
+ ** then all such updates are considered CONSTRAINT conflicts.
12856
12867
  */
12857
12868
  #define SQLITE_CHANGESETAPPLY_NOSAVEPOINT 0x0001
12858
12869
  #define SQLITE_CHANGESETAPPLY_INVERT 0x0002
12859
12870
  #define SQLITE_CHANGESETAPPLY_IGNORENOOP 0x0004
12860
12871
  #define SQLITE_CHANGESETAPPLY_FKNOACTION 0x0008
12872
+ #define SQLITE_CHANGESETAPPLY_NOUPDATELOOP 0x0010
12861
12873
 
12862
12874
  /*
12863
12875
  ** CAPI3REF: Constants Passed To The Conflict Handler
@@ -19,7 +19,7 @@
19
19
  # ===
20
20
 
21
21
  YEAR="2026"
22
- VERSION="3530100"
22
+ VERSION="3530200"
23
23
 
24
24
  # Defines below are sorted alphabetically
25
25
  DEFINES="