erdbpro 2.4.5-beta.3 → 2.4.5-beta.5
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.
- package/dist/assets/index-Bmk-1vOU.js +12701 -0
- package/dist/index.html +1 -1
- package/dist-server/node_modules/better-sqlite3/build/Release/.deps/4292fa9a667d77b27488aa109b010a85bce8e4e7a1c7aa0370cea902395c3866.intermediate.d +1 -1
- package/dist-server/node_modules/better-sqlite3/build/Release/.deps/Release/obj.target/better_sqlite3/src/better_sqlite3.o.d.raw +82 -0
- package/dist-server/node_modules/better-sqlite3/build/Release/.deps/Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o.d +4 -0
- package/dist-server/node_modules/better-sqlite3/build/Release/.deps/Release/sqlite3.a.d +1 -0
- package/dist-server/node_modules/better-sqlite3/build/Release/better_sqlite3.node +0 -0
- package/dist-server/node_modules/better-sqlite3/deps/download.sh +1 -1
- package/dist-server/node_modules/better-sqlite3/deps/sqlite3/sqlite3.c +692 -176
- package/dist-server/node_modules/better-sqlite3/deps/sqlite3/sqlite3.h +17 -5
- package/dist-server/node_modules/better-sqlite3/package.json +1 -1
- package/dist-server/node_modules/better-sqlite3/src/better_sqlite3.cpp +1 -1
- package/dist-server/node_modules/better-sqlite3/src/util/helpers.cpp +1 -1
- package/dist-server/node_modules/better-sqlite3/src/util/macros.cpp +8 -1
- package/package.json +1 -1
|
@@ -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.
|
|
150
|
-
#define SQLITE_VERSION_NUMBER
|
|
151
|
-
#define SQLITE_SOURCE_ID "2026-
|
|
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.
|
|
154
|
-
#define SQLITE_SCM_DATETIME "2026-
|
|
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
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "better-sqlite3",
|
|
3
|
-
"version": "12.
|
|
3
|
+
"version": "12.11.1",
|
|
4
4
|
"description": "The fastest and simplest library for SQLite in Node.js.",
|
|
5
5
|
"homepage": "http://github.com/WiseLibs/better-sqlite3",
|
|
6
6
|
"author": "Joshua Wise <joshuathomaswise@gmail.com>",
|
|
@@ -57,7 +57,7 @@ NODE_MODULE_INIT(/* exports, context */) {
|
|
|
57
57
|
|
|
58
58
|
// Initialize addon instance.
|
|
59
59
|
Addon* addon = new Addon(isolate);
|
|
60
|
-
v8::Local<v8::External> data =
|
|
60
|
+
v8::Local<v8::External> data = EXTERNAL_NEW(isolate, addon);
|
|
61
61
|
node::AddEnvironmentCleanupHook(isolate, Addon::Cleanup, addon);
|
|
62
62
|
|
|
63
63
|
// Create and export native-backed classes and functions.
|
|
@@ -27,7 +27,14 @@
|
|
|
27
27
|
#define EasyIsolate v8::Isolate* isolate = v8::Isolate::GetCurrent()
|
|
28
28
|
#define OnlyIsolate info.GetIsolate()
|
|
29
29
|
#define OnlyContext isolate->GetCurrentContext()
|
|
30
|
-
#
|
|
30
|
+
#if defined(NODE_MODULE_VERSION) && NODE_MODULE_VERSION >= 146
|
|
31
|
+
#define EXTERNAL_NEW(isolate, value) v8::External::New((isolate), (value), 0)
|
|
32
|
+
#define EXTERNAL_VALUE(value) (value)->Value(0)
|
|
33
|
+
#else
|
|
34
|
+
#define EXTERNAL_NEW(isolate, value) v8::External::New((isolate), (value))
|
|
35
|
+
#define EXTERNAL_VALUE(value) (value)->Value()
|
|
36
|
+
#endif
|
|
37
|
+
#define OnlyAddon static_cast<Addon*>(EXTERNAL_VALUE(info.Data().As<v8::External>()))
|
|
31
38
|
#define UseIsolate v8::Isolate* isolate = OnlyIsolate
|
|
32
39
|
#define UseContext v8::Local<v8::Context> ctx = OnlyContext
|
|
33
40
|
#define UseAddon Addon* addon = OnlyAddon
|