mirror of
https://github.com/hanzoai/base.git
synced 2026-10-21 03:41:50 +00:00
zeekay
d9f7c4da8e
BASE_DB_TIER=sql opened PostgreSQL and then spoke to it in SQLite: strftime, sqlite_master, json_extract, json_each, an INTEGER column holding an int64, an outer join with no ON, backticked identifiers, and a rowid that only one engine has. The tier picked a backend the queries could not reach. Every one of those now comes from hanzoai/orm/dialect, resolved once from the driver the data DB was opened with and reachable as app.Dialect(). Base holds no switch on the engine — it asks for the JSON accessors, the schema catalog, the generated instant and identifier, and the column types, and it asks whether a feature exists at all where one engine has nothing to offer: an insertion-order column, a write-ahead log to fold, a function that renders an instant. Empty means the caller falls back or refuses rather than emitting something the engine will reject. Some differences turned out not to need a dialect at all. An instant is stored as text in a fixed layout, so bucketing the log rollup to the hour is a substring rather than a calendar function, which every engine spells the same way and an index can be built on. Null-safe equality is IS NOT DISTINCT FROM. An int64 column is BIGINT. A join with nothing of its own to match still states a condition. Case-insensitive comparison stays COLLATE NOCASE, because the schema now asks the engine for the collation that name refers to. The proof is a Postgres 18 running the data plane: migrations apply, a collection created over /v1 lands as a table with text, numeric and jsonb columns and its declared index, and records insert, page, sort, filter across scalars, multi-value elements and JSON paths, update and delete. A unique index declared COLLATE NOCASE rejects the second spelling of a handle. Comparing a JSON sub-path to a number is refused there: the extraction yields text, the literal binds as a number, and the filter language does not say which the comparison meant. Compared as text it works.
46 lines
1.1 KiB
Go
46 lines
1.1 KiB
Go
package dbutils_test
|
|
|
|
import (
|
|
"strings"
|
|
"testing"
|
|
|
|
"github.com/hanzoai/base/tools/dbutils"
|
|
"github.com/hanzoai/orm/dialect"
|
|
)
|
|
|
|
// The engine's spelling is the dialect's to get right, and it is tested there
|
|
// by executing it. What this layer owes its callers is the bracketing dbx
|
|
// expects around a column name, and a path that reads as a member unless it
|
|
// already opens with an index.
|
|
|
|
func TestJSONColumnIsBracketed(t *testing.T) {
|
|
d := dialect.For("sqlite")
|
|
|
|
for name, got := range map[string]string{
|
|
"each": dbutils.JSONEach(d, "a.b"),
|
|
"length": dbutils.JSONArrayLength(d, "a.b"),
|
|
"extract": dbutils.JSONExtract(d, "a.b", ""),
|
|
} {
|
|
if strings.Contains(got, "[[a.b]]") {
|
|
continue
|
|
}
|
|
t.Errorf("%s did not bracket the column: %s", name, got)
|
|
}
|
|
}
|
|
|
|
func TestJSONExtractPath(t *testing.T) {
|
|
d := dialect.For("sqlite")
|
|
|
|
for path, want := range map[string]string{
|
|
"": "'$'",
|
|
"a": "'$.a'",
|
|
"a.b": "'$.a.b'",
|
|
"[0]": "'$[0]'",
|
|
"[0].a": "'$[0].a'",
|
|
} {
|
|
if got := dbutils.JSONExtract(d, "col", path); !strings.Contains(got, want) {
|
|
t.Errorf("path %q produced %s, wanted it to carry %s", path, got, want)
|
|
}
|
|
}
|
|
}
|