@undefineds.co/drizzle-solid 0.2.13 → 0.3.1

package/CHANGELOG-DRAFT.md

@@ -392,7 +392,7 @@ npm test
 - [CSS Notifications](./docs/guides/css-notifications.md) - 实时通知支持（79KB）
 
 ### 开发指南
-- [测试策略](./TESTING_STRATEGY.md) - 测试方法和覆盖
+- [测试指南](./docs/guides/testing.md) - 当前测试方法、分层和验证要求
 - [快速开始](./docs/quick-start-local.md) - 本地开发入门
 - [文档索引](./docs/README.md) - 完整文档导航
 

package/README.md

@@ -1,123 +1,103 @@
 # drizzle-solid
 
-`drizzle-solid` is a Drizzle-aligned adapter for application-owned data in Solid Pods.
+`drizzle-solid` is a Drizzle-aligned data layer for application-owned data in Solid Pods.
 
-It helps you define typed models, map them to RDF resources/documents/IRIs, and read or write them with a familiar query builder — without pretending Solid is a relational database.
+这次变化的重点不是强迫你把构造函数名字从 `drizzle()` 换成别的东西，而是把语义讲清楚：
 
-The library is intentionally **document-first**, **IRI-native**, **Pod-aware**, and **SPARQL-native**.
+- `table` 更接近 **resource layout / collection definition**
+- `link` 字段更接近 **RDF link / IRI link**
+- 实体最终身份更接近 **IRI / @id**，而不只是本地主键
+- 读取和写入不再默认共享 SQL 式语义
 
-## What it helps with
+## Scope
 
-- Defining typed application data for Solid Pods
-- Mapping fields to RDF predicates and resource layouts
-- Using a Drizzle-style CRUD/query builder over Pod data
-- Performing exact entity operations through full IRIs
-- Building discovery, federation, and notification flows on top of Solid-native storage
+Current v1 solves one problem well:
 
-## Design principles
+- persist application-owned data into Solid Pods with typed schemas
+- keep Pod layout explicit through `base` and `subjectTemplate`
+- make full IRIs part of the public API instead of hiding them behind local-only IDs
+- give Drizzle users a migration-friendly surface without pretending Solid is a SQL database
+- support adjacent Solid flows such as discovery, notifications, and federation where they fit the Pod model
 
-- **Document-first**: model around Solid resources and document boundaries
-- **IRI-native**: treat IRIs as first-class identity, not as an afterthought over local IDs
-- **Pod-aware**: keep resource layout, links, network, and access constraints explicit
-- **Drizzle-aligned**: stay close to Drizzle's builder surface and ergonomics where it makes sense
-- **SPARQL-native**: the native query model is SPARQL/Solid, not SQL emulation
+Not in v1:
 
-## What it is
-
-- A typed persistence layer for application-owned data in Solid Pods
-- A Drizzle-style API surface over RDF resources and documents
-- A practical bridge for teams migrating Drizzle mental models into Solid-native data flows
-
-## What it isn't
-
-- Not a general-purpose SQL ORM
-- Not a universal abstraction over arbitrary RDF on the open web
-- Not a graph database or SPARQL engine replacement
-- Not a black box that hides Pod boundaries, permissions, or network behavior
-- Not a promise that every SQL/driver-specific Drizzle feature maps cleanly to Solid
-
-## Core concepts
-
-### Resource
-
-A resource is the persisted unit in a Pod, usually a Turtle or JSON-LD document addressed by URL.
-
-### Document
-
-A document may contain one entity or many entities. Document layout is part of application design, not an implementation detail.
-
-### Entity
-
-An entity is a typed RDF subject stored in a document. It is closer to a linked-data subject than to a relational row.
+- full SQL/database feature parity
+- raw SQL as the primary abstraction
+- hiding Pod boundaries, permissions, or network behavior
+- implicit scan-based `updateMany/deleteMany` on backends that do not support set-based mutation
+- universal querying over arbitrary open-world RDF as the main goal
 
-### IRI
+## Constructor Choice
 
-IRIs are native identity. `drizzle-solid` keeps the full subject IRI available and provides explicit IRI APIs for exact operations.
+仓库文档与 examples 默认先用 `pod(session, config?)` 讲主线语义：
 
-### Link
+- `pod(session, config?)`
+- `drizzle(session, config?)`
 
-Links between entities are represented as IRIs and may cross documents or Pods.
+建议这样理解：
 
-### Model
+- `pod()` 是语义优先的正式入口，方便把 API 组织成 `collection()` / `entity()` / `bind()`
+- `drizzle()` 是同一运行时上的 Drizzle-aligned 入口，适合迁移或保留 builder/query 代码形状
+- 重要的不是“入口名”，而是下面这些语义：`base`、`subjectTemplate`、`IRI`、exact-target mutation
 
-`drizzle-solid` supports two modeling styles:
+## Public Surface
 
-- `podTable(...)`: schema plus concrete storage location
-- `solidSchema(...)` + `db.createTable(...)`: reusable schema separated from where data is stored
+当前公开表面可以分成两层：
 
-### Pod client
+### Semantic-first surface
 
-`drizzle(session)` creates the database client bound to an authenticated Solid session.
+- `pod(session, config?)`
+- `client.bind(schema, options)`
+- `client.collection(table)`
+- `client.entity(table, iri)`
+- `client.sparql(query)`
 
-## Modeling vs persistence
+### Drizzle-aligned surface
 
-A Solid application usually needs to answer two different questions:
+- `drizzle(session, config?)`
+- `podTable(name, columns, config)`
+- `solidSchema(...)`
+- `select / insert / update / delete`
+- `db.query.*` read facade
 
-1. **What is the shape of my data?**
-2. **Where does that data live in Pods?**
+## Install
 
-`drizzle-solid` keeps those concerns explicit.
+```bash
+yarn add @undefineds.co/drizzle-solid drizzle-orm
+# optional, when your app wants the default SPARQL client engine
+yarn add @comunica/query-sparql-solid
+```
 
-- Use `podTable(...)` when your app owns the storage location and you want one place to define shape + location.
-- Use `solidSchema(...)` when the same schema should be reused across different Pod locations, profiles, or discovered data sources.
-- Use `db.createTable(schema, { base, ... })` when you want to bind a reusable schema to a concrete place at runtime.
+```bash
+npm install @undefineds.co/drizzle-solid drizzle-orm
+npm install @comunica/query-sparql-solid
+```
 
-This keeps Solid's persistence model visible instead of flattening everything into table-only abstractions.
+`@comunica/query-sparql-solid` is an optional peer dependency.
 
-## Why document-first
+Install it in the consuming app when you need built-in SPARQL query execution or direct SPARQL workflows.
 
-Solid stores data in resources, not in tables.
+Without a SPARQL endpoint or index, plain-LDP document mode is limited to exact-target access (`findByLocator` / `findByIri` and the matching update/delete APIs). Collection queries are not implicitly expanded into scans.
 
-That means application design starts with questions like:
+Current public compatibility stance:
 
-- which entities belong in the same document
-- which entities should be split into separate resources
-- which resources should be public, private, or shared
-- how links should work across documents and Pods
+- officially supported: `@comunica/query-sparql-solid` `4.x`
+- not currently in the supported matrix: `3.x`
 
-`drizzle-solid` follows that reality. It provides a structured API, but keeps resource identity and document layout as part of the model.
+If another in-process runtime already carries Comunica (for example `xpod`), inject that engine instead of forcing a second copy. See `docs/api/README.md` and `docs/guides/installation.md`.
 
 ## Quick start
 
-### Install
-
-```bash
-yarn add @undefineds.co/drizzle-solid
-# or
-npm install @undefineds.co/drizzle-solid
-```
-
-> In this repository, the examples import `drizzle-solid` through a local TypeScript path alias. In external applications, import the published package name: `@undefineds.co/drizzle-solid`.
+仓库里的主线 quick start 默认使用 `pod(session)`，因为它会把 `collection()` / `entity()` / `bind()` 语义直接写在代码里。
 
-### Define a model and run CRUD
+如果你已有大量 Drizzle 风格代码，`drizzle(session)` 仍然是正式可用入口。
 
 ```ts
 import {
-  drizzle,
+  pod,
   podTable,
   string,
   datetime,
-  eq,
 } from '@undefineds.co/drizzle-solid';
 
 const posts = podTable('posts', {
@@ -131,115 +111,100 @@ const posts = podTable('posts', {
   type: 'http://schema.org/CreativeWork',
 });
 
-const db = drizzle(session);
-await db.init([posts]);
+const client = pod(session);
+await client.init(posts);
 
-await db.insert(posts).values({
+const postsCollection = client.collection(posts);
+
+const created = await postsCollection.create({
   id: 'post-1',
   title: 'Hello Solid',
   content: 'Stored as RDF in a Pod document.',
   createdAt: new Date(),
 });
 
-const rows = await db.select()
-  .from(posts)
-  .where(eq(posts.id, 'post-1'));
+const first = await postsCollection.first({
+  where: { id: 'post-1' },
+});
 
-await db.update(posts)
-  .set({ title: 'Updated title' })
-  .where(eq(posts.id, 'post-1'));
+const postIri = created?.['@id'] ?? postsCollection.iriFor({
+  id: 'post-1',
+  title: 'Hello Solid',
+  content: 'Stored as RDF in a Pod document.',
+  createdAt: new Date(),
+});
 
-await db.delete(posts)
-  .where(eq(posts.id, 'post-1'));
+const post = client.entity(posts, postIri);
+await post.update({ title: 'Updated title' });
+await post.delete();
 ```
 
-### Reusable schema + runtime binding
+> 如果你保持 `drizzle(session)` 作为入口，语义并不会变：`base`、`subjectTemplate`、`IRI`、精确写目标这些约束仍然完全成立。
 
-```ts
-import {
-  drizzle,
-  solidSchema,
-  id,
-  string,
-} from '@undefineds.co/drizzle-solid';
+## Reusable schema + runtime binding
 
-const profileSchema = solidSchema({
-  id: id(),
-  name: string('name').predicate('http://xmlns.com/foaf/0.1/name'),
-  bio: string('bio').predicate('http://schema.org/description'),
-}, {
-  type: 'http://xmlns.com/foaf/0.1/Person',
+Use `solidSchema(...)` when you want to separate the reusable data shape from where that data lives in a Pod.
+
+如果你使用 `pod()` façade：
+
+```ts
+const client = pod(session);
+const profileTable = client.bind(profileSchema, {
+  base: 'https://alice.example/profile/card',
 });
+```
 
-const db = drizzle(session);
+如果你保持 `drizzle()` 入口：
 
+```ts
+const db = drizzle(session);
 const profileTable = db.createTable(profileSchema, {
   base: 'https://alice.example/profile/card',
 });
 ```
 
-## Exact IRI operations
+## Identity and placement
 
-For detail-page flows, remote links, shared resources, or exact mutation targets, use the IRI APIs:
+`subjectTemplate` defines how application identity maps onto Pod resources.
 
-- `db.findByIri(table, iri)`
-- `db.updateByIri(table, iri, data)`
-- `db.deleteByIri(table, iri)`
-- `db.subscribeByIri(table, iri, options)`
+Common patterns:
 
-```ts
-const agent = await db.findByIri(agentTable, 'https://alice.example/data/agents.ttl#assistant');
-
-await db.updateByIri(
-  agentTable,
-  'https://alice.example/data/agents.ttl#assistant',
-  { description: 'Updated through explicit IRI' },
-);
-
-await db.deleteByIri(
-  agentTable,
-  'https://alice.example/data/agents.ttl#assistant',
-);
-```
+- `#{id}`: many entities inside one document
+- `{id}.ttl`: one document per entity
+- `{id}.ttl#it`: one document per entity with stable in-document fragment
+- `{chatId}/messages.ttl#{id}`: multi-variable layouts and partitioned resources
 
-## Subject templates and identity
+If a layout uses multiple template variables, exact lookup is only exact when all required locator variables are present, or when you already hold the full IRI.
 
-`subjectTemplate` controls how record identity maps to Pod resources.
+这不是命名细节，而是持久化语义本身。
 
-Common patterns:
+## Type hierarchy
 
-- `#{id}`: fragment mode, many entities in one RDF file
-- `{id}.ttl`: document mode, one file per entity
-- `{id}.ttl#it`: document mode with stable in-document fragment
-- `{chatId}/{yyyy}/{MM}/{dd}/messages.ttl#{id}`: multi-variable, date-partitioned layouts
+Class hierarchy and instance typing are not the same thing.
 
-Example:
+- `type` is the primary persisted `rdf:type` for an entity
+- `subClassOf` expresses schema / vocabulary hierarchy
+- by default, persisted instance data should keep one most-specific, authoritative `rdf:type`
+- do not persist both a base/table type and a business subtype on the same entity unless they carry genuinely different semantics
+- do not introduce parallel string-based type systems when the meaning is already carried by RDF class membership
+- if parent types must be materialized for no-inference environments, treat that as an explicit compatibility mode rather than the default stored shape
 
-```ts
-const Message = podTable('Message', {
-  id: string('id').primaryKey(),
-  chatId: string('chatId').predicate('http://example.org/chatId'),
-  content: string('content').predicate('http://schema.org/text'),
-  timestamp: datetime('timestamp').predicate('http://schema.org/dateCreated'),
-}, {
-  base: 'https://alice.example/data/chats/',
-  subjectTemplate: '{chatId}/messages.ttl#{id}',
-  type: 'http://schema.org/Message',
-});
-```
+## Exact-target mutation semantics
 
-For reads, the library can often work from:
+Reads and writes do not intentionally behave the same way.
 
-- a full IRI
-- all template variables
-- a narrower partial condition that scans a smaller bounded area
+- list / filter reads can stay collection-oriented
+- writes should prefer exact-target semantics
+- if an API path semantically requires exact-target resolution, it should remain exact or fail explicitly; do not silently widen it into scan-style execution
+- incomplete `where(...)` information should not silently degrade into scan + mutate
+- if a subject can only be resolved by multiple template variables, mutation should use an explicit IRI or provide all required variables
+- join on a multi-variable target should also provide all required locator variables, or join via full IRI values
+- do not silently degrade unresolved multi-variable joins into scan-style fallback
 
-Read-path and write-path semantics are intentionally different:
+所以最重要的变化不是“要不要换成 `pod()`”，而是：
 
-- **Read queries** (`select`, `db.query.*`) may use partial template information for list/filter flows when the resolver can keep the scan bounded.
-- **Mutations** (`update`, `delete`) require deterministic targets by default. If `where()` cannot uniquely resolve the subject from the template, the dialect throws and tells you to use `updateByIri()` / `deleteByIri()` (or to provide the missing template variables).
-- **No implicit scan-based `updateMany/deleteMany` fallback** is performed on backends that do not natively support set-based mutation.
-- **Capability-based enhancement**: if a backend explicitly supports filter-based multi-row mutation in the future (for example, an xpod capability), `drizzle-solid` can expose that path there without pretending every Solid server supports it.
+- 什么时候你只是在做集合读取
+- 什么时候你已经需要一个确定的实体目标
 
 ## Server support
 
@@ -247,118 +212,68 @@ Read-path and write-path semantics are intentionally different:
 
 | Capability | Community Solid Server | xpod |
 | --- | --- | --- |
-| Basic CRUD | ✅ LDP mode | ✅ LDP mode |
-| SPARQL SELECT pushdown | ❌ Client-side / resolver-driven | ✅ `/-/sparql` sidecar |
-| SPARQL UPDATE | ⚠️ Limited / write path stays LDP-oriented | ✅ Better server-side support |
-| Filter / aggregation pushdown | ❌ Fallbacks and client execution | ✅ Single-Pod pushdown |
+| Basic CRUD | ✅ | ✅ |
+| Document notifications | ✅ | ✅ |
+| Drizzle-style read facade | ✅ | ✅ |
+| SPARQL pushdown | ⚠️ Limited / often client-assisted | ✅ Better in-process support |
+| Filter / aggregation pushdown | ❌ Mostly fallback execution | ✅ Better server-side support |
 | Federated queries | ⚠️ Client-side federation | ⚠️ Client-side federation |
-| Notifications | ✅ | ✅ |
-| In-process test runtime | ⚠️ External CSS setup | ✅ via `@undefineds.co/xpod` |
-
-### Community Solid Server (CSS)
-
-On plain CSS, `drizzle-solid` keeps working, but many queries are resolved through client-side execution and Solid-aware fallbacks. This is the compatibility baseline.
-
-### xpod
+| In-process local runtime | ⚠️ External setup | ✅ via `@undefineds.co/xpod` |
 
-`xpod` adds a Solid-compatible SPARQL sidecar and is the recommended development/runtime target when you want stronger query pushdown and a lower-friction local setup.
-
-See `docs/xpod-features.md` for more detail.
+If `xpod` already ships its own Comunica stack, `drizzle-solid` can reuse that copy instead of requiring another app-level install.
 
 ## Verified examples
 
-The canonical examples in `examples/` are verified in the test suite.
-
-- `examples/01-quick-start.ts` — CRUD quick start
-- `examples/02-relational-query.ts` — relational query API surface
-- `examples/03-zero-config-discovery.ts` — zero-config discovery flow
-- `examples/04-notifications.ts` — Solid notifications
-- `examples/05-data-discovery.ts` — discovery API
-- `examples/06-federated-query.ts` — federated query across Pods
-- `examples/07-hooks-and-profile.ts` — hooks and profile management
-- `examples/08-iri-based-operations.ts` — explicit IRI operations
-- `examples/08-schema-inheritance.ts` — schema inheritance
-- `examples/09-multi-variable-templates.ts` — multi-variable subject templates
-
-The example manifest lives at `examples/manifest.json`, and the integration verification lives at `tests/integration/css/examples-verification.test.ts`.
-
-## Query surface and SQL scope
-
-`drizzle-solid` aims to stay close to Drizzle's public builder surface where that maps cleanly to Solid.
+The canonical examples in `examples/` are part of the real integration verification flow:
 
-Current supported surface includes:
+- `examples/01-quick-start.ts`
+- `examples/02-relational-query.ts`
+- `examples/03-zero-config-discovery.ts`
+- `examples/04-notifications.ts`
+- `examples/05-data-discovery.ts`
+- `examples/06-federated-query.ts`
+- `examples/07-hooks-and-profile.ts`
+- `examples/08-iri-based-operations.ts`
+- `examples/08-schema-inheritance.ts`
+- `examples/09-multi-variable-templates.ts`
 
-- CRUD builders: `select`, `insert`, `update`, `delete`
-- Read-oriented query facade: `db.query.*.findMany`, `findFirst`, `findById`, `findByIRI`, `count`
-- Conditions: `eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `like`, `ilike`, `inArray`, `exists`, `and`, `or`, `not`
-- Query features: joins, ordering, limits, offsets, distinct
-- Aggregations: `count`, `sum`, `avg`, `min`, `max`
-- Batch and `returning()` support where implemented by the dialect
-- Raw **SPARQL** workflows where you need explicit graph-native control
-
-Not the mainline contract:
-
-- raw SQL as the primary abstraction
-- transaction semantics identical to SQL databases
-- implicit scan-based `updateMany/deleteMany` on backends that do not support set-based mutation
-- driver-specific DDL, auto-increment, foreign keys, or SQL engine behaviors
+See `examples/manifest.json` and `tests/integration/css/examples-verification.test.ts`.
 
-The migration goal is API familiarity with low migration cost, but the execution model remains Solid/SPARQL-native rather than semantics-faking SQL emulation.
+## Migration
 
-## Discovery, interoperability, and federation
+If you already know `drizzle-orm`, start here:
 
-The library also includes higher-level Solid workflows:
+- `docs/guides/migrating-from-drizzle-orm.md`
 
-- data discovery and interop metadata
-- TypeIndex-driven location discovery
-- shape-aware table generation
-- federated queries across discovered Pod locations
-- notifications for resource/entity updates
+那份指南重点解释的是：
 
-Useful starting points:
+- `table/row` → `resource/document/entity/IRI`
+- `link` / relation fields → RDF link / IRI link
+- `where`-style mutation → exact-target mutation
+- `toSQL()` / raw SQL 主心智 → `toSPARQL()` / SPARQL 主心智
 
-- `docs/guides/data-discovery.md`
-- `docs/guides/notifications.md`
-- `docs/guides/css-notifications.md`
-- `docs/federated-queries.md`
-- `docs/guides/multi-variable-templates.md`
+而不是要求你第一步先改掉构造函数名。
 
 ## Documentation map
 
-- `examples/README.md` — curated walkthroughs and runnable examples
-- `docs/quick-start-local.md` — local setup guide
+- `docs/api/README.md` — current public API and constructor positioning
+- `docs/guides/installation.md` — installation and SPARQL engine setup
+- `docs/guides/migrating-from-drizzle-orm.md` — migration guide for Drizzle users
+- `docs/guides/testing.md` — canonical testing policy, verification layers, and execution-path guardrails
+- `docs/guides/context7-and-skills.md` — Context7 publication scope, skills plan, and feedback flow
+- `docs/guides/issue-triage.md` — classify code, docs, tooling, and decision issues
+- `docs/guides/modeling-consensus.md` — when modeling questions require multi-AI consensus instead of a single answer
+- `docs/guides/decisions/README.md` — decision records and the template for stable repo-wide conclusions
+- `skills/README.md` — canonical public skill pack source for future Context7 Skills publishing
+- `examples/README.md` — curated runnable examples
 - `docs/guides/data-discovery.md` — discovery workflows
-- `docs/guides/issue-handling.md` — issue reproduction and regression workflow
-- `docs/guides/testing.md` — test conventions and coverage strategy
-- `ACTION-PLAN.md` — current parity and implementation plan
-
-## Planned scope
-
-### Current direction
-
-The current focus is:
-
-- typed models for application-owned Pod data
-- explicit document and subject placement
-- Drizzle-aligned query ergonomics
-- practical CRUD, discovery, federation, and notification flows
-
-### Likely next steps
-
-- better modeling ergonomics around reusable schemas and links
-- clearer guidance around multi-resource layouts and identity strategies
-- continued Drizzle parity on Solid-relevant behaviors
-- stronger documentation around Solid-native tradeoffs and migration paths
-
-### Out of scope
-
-- hiding Solid behind a fake SQL database mental model
-- universal querying over arbitrary open-world RDF as the primary goal
-- promising full relational/database feature parity where Solid semantics differ
+- `docs/guides/notifications.md` — notification flows
+- `docs/xpod-features.md` — xpod runtime notes
+- `ACTION-PLAN.md` — testing/parity backlog and execution log, not the testing policy
 
 ## Contributing
 
-Before contributing:
+Before pushing:
 
 ```bash
 yarn build

package/dist/core/ast-to-sparql.d.ts

@@ -1,9 +1,25 @@
 import { SQL } from 'drizzle-orm';
-import { PodTable } from './schema';
+import { PodColumnBase, PodTable } from './schema';
 import { SPARQLQuery } from './sparql/types';
 import { SelectQueryPlan } from './select-plan';
+import { QueryCondition } from './query-conditions';
 import type { UriResolver } from './uri';
 export type { SPARQLQuery };
+interface SimpleSelectOperation {
+    table: PodTable;
+    where?: Record<string, unknown>;
+    limit?: number;
+    offset?: number;
+    orderBy?: Array<{
+        column: string;
+        direction: 'asc' | 'desc';
+    }>;
+    distinct?: boolean;
+}
+interface InsertPlanInput {
+    table: PodTable;
+    rows: Array<Record<string, unknown>>;
+}
 /**
  * Table registry context for URI resolution
  */
@@ -23,35 +39,26 @@ export declare class ASTToSPARQLConverter {
     private prefixes;
     constructor(podUrl: string, webId?: string | undefined, uriResolver?: UriResolver);
     /**
-     * Set table registry for URI reference resolution
+     * Set table registry for URI link resolution
      */
     setTableRegistry(tableRegistry: Map<string, PodTable[]>, tableNameRegistry: Map<string, PodTable>, baseUri?: string): void;
-    convertSelect(ast: any, table: PodTable, targetGraph?: string, fromSources?: string[], allowGraphVariable?: boolean): SPARQLQuery;
-    buildWhereClauseForCondition(whereAst: any, table: PodTable): string;
+    convertSelect(ast: Record<string, unknown>, table: PodTable, targetGraph?: string, fromSources?: string[], allowGraphVariable?: boolean): SPARQLQuery;
+    buildWhereClauseForCondition(whereAst: QueryCondition, table: PodTable): string;
     convertSelectPlan(plan: SelectQueryPlan, targetGraph?: string, fromSources?: string[], allowGraphVariable?: boolean): SPARQLQuery;
-    convertSimpleSelect(operation: {
-        table: PodTable;
-        where?: Record<string, unknown>;
-        limit?: number;
-        offset?: number;
-        orderBy?: Array<{
-            column: string;
-            direction: 'asc' | 'desc';
-        }>;
-        distinct?: boolean;
-    }, targetGraph?: string, fromSources?: string[], allowGraphVariable?: boolean): SPARQLQuery;
-    convertInsert(valuesOrPlan: any[] | {
-        table: PodTable;
-        rows: any[];
-    }, table?: PodTable, targetGraph?: string): SPARQLQuery;
-    convertUpdate(setData: any, whereConditions: any, table: PodTable, targetGraph?: string): SPARQLQuery;
-    convertDelete(whereConditions: any, table: PodTable, targetGraph?: string): SPARQLQuery;
+    convertSimpleSelect(operation: SimpleSelectOperation, targetGraph?: string, fromSources?: string[], allowGraphVariable?: boolean): SPARQLQuery;
+    convertInsert(valuesOrPlan: Array<Record<string, unknown>> | InsertPlanInput, table?: PodTable, targetGraph?: string): SPARQLQuery;
+    convertUpdate(setData: Record<string, unknown>, whereConditions: QueryCondition | Record<string, unknown>, table: PodTable, targetGraph?: string): SPARQLQuery;
+    convertDelete(whereConditions: QueryCondition | Record<string, unknown>, table: PodTable, targetGraph?: string): SPARQLQuery;
     getPrefixes(): Record<string, string>;
     addPrefix(prefix: string, uri: string): void;
-    getPredicateForColumnPublic(column: any, table: PodTable): string;
-    formatLiteralValue(value: any, column?: any): string | string[];
-    generateSubjectUri(record: any, table: PodTable): string;
-    parseDrizzleAST(sql: SQL, _table?: PodTable): any;
+    getPredicateForColumnPublic(column: PodColumnBase | string | Record<string, unknown>, table: PodTable): string;
+    formatLiteralValue(value: unknown, column?: PodColumnBase | Record<string, unknown>): string | string[];
+    generateSubjectUri(record: Record<string, unknown>, table: PodTable): string;
+    parseDrizzleAST(sql: SQL, _table?: PodTable): {
+        type: 'select';
+        columns: '*';
+        where: Record<string, never>;
+    };
     private parseWhereClause;
 }
 //# sourceMappingURL=ast-to-sparql.d.ts.map

package/dist/core/ast-to-sparql.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ast-to-sparql.d.ts","sourceRoot":"","sources":["../../src/core/ast-to-sparql.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,GAAG,EAAE,MAAM,aAAa,CAAC;AAClC,OAAO,EAAE,QAAQ,EAAE,MAAM,UAAU,CAAC;AAGpC,OAAO,EAAE,WAAW,EAAE,MAAM,gBAAgB,CAAC;AAC7C,OAAO,EAAE,eAAe,EAAE,MAAM,eAAe,CAAC;AAIhD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,OAAO,CAAC;AAGzC,YAAY,EAAE,WAAW,EAAE,CAAC;AAE5B;;GAEG;AACH,MAAM,WAAW,oBAAoB;IACnC,aAAa,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,EAAE,CAAC,CAAC;IACvC,iBAAiB,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;IACzC,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB;AAED,qBAAa,oBAAoB;IAiBnB,OAAO,CAAC,MAAM;IAAU,OAAO,CAAC,KAAK,CAAC;IAhBlD,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,iBAAiB,CAAoB;IAC7C,OAAO,CAAC,YAAY,CAAC,CAAuB;IAC5C,OAAO,CAAC,WAAW,CAAc;IACjC,OAAO,CAAC,QAAQ,CASd;gBAEkB,MAAM,EAAE,MAAM,EAAU,KAAK,CAAC,EAAE,MAAM,YAAA,EAAE,WAAW,CAAC,EAAE,WAAW;IAOrF;;OAEG;IACH,gBAAgB,CACd,aAAa,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,EAAE,CAAC,EACtC,iBAAiB,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,CAAC,EACxC,OAAO,CAAC,EAAE,MAAM,GACf,IAAI;IAOP,aAAa,CAAC,GAAG,EAAE,GAAG,EAAE,KAAK,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,EAAE,kBAAkB,UAAO,GAAG,WAAW;IAI9H,4BAA4B,CAAC,QAAQ,EAAE,GAAG,EAAE,KAAK,EAAE,QAAQ,GAAG,MAAM;IAIpE,iBAAiB,CAAC,IAAI,EAAE,eAAe,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,EAAE,kBAAkB,UAAO,GAAG,WAAW;IAI9H,mBAAmB,CAAC,SAAS,EAAE;QAC7B,KAAK,EAAE,QAAQ,CAAC;QAChB,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;QAChC,KAAK,CAAC,EAAE,MAAM,CAAC;QACf,MAAM,CAAC,EAAE,MAAM,CAAC;QAChB,OAAO,CAAC,EAAE,KAAK,CAAC;YAAE,MAAM,EAAE,MAAM,CAAC;YAAC,SAAS,EAAE,KAAK,GAAG,MAAM,CAAA;SAAE,CAAC,CAAC;QAC/D,QAAQ,CAAC,EAAE,OAAO,CAAC;KACpB,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,EAAE,kBAAkB,UAAO,GAAG,WAAW;IAIxF,aAAa,CAAC,YAAY,EAAE,GAAG,EAAE,GAAG;QAAE,KAAK,EAAE,QAAQ,CAAC;QAAC,IAAI,EAAE,GAAG,EAAE,CAAA;KAAE,EAAE,KAAK,CAAC,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,GAAG,WAAW;IAI1H,aAAa,CAAC,OAAO,EAAE,GAAG,EAAE,eAAe,EAAE,GAAG,EAAE,KAAK,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,GAAG,WAAW;IAIrG,aAAa,CAAC,eAAe,EAAE,GAAG,EAAE,KAAK,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,GAAG,WAAW;IAIvF,WAAW,IAAI,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC;IAIrC,SAAS,CAAC,MAAM,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,IAAI;IAM5C,2BAA2B,CAAC,MAAM,EAAE,GAAG,EAAE,KAAK,EAAE,QAAQ,GAAG,MAAM;IAIjE,kBAAkB,CAAC,KAAK,EAAE,GAAG,EAAE,MAAM,CAAC,EAAE,GAAG,GAAG,MAAM,GAAG,MAAM,EAAE;IAI/D,kBAAkB,CAAC,MAAM,EAAE,GAAG,EAAE,KAAK,EAAE,QAAQ,GAAG,MAAM;IAIxD,eAAe,CAAC,GAAG,EAAE,GAAG,EAAE,MAAM,CAAC,EAAE,QAAQ,GAAG,GAAG;IASjD,OAAO,CAAC,gBAAgB;CAIzB"}
+{"version":3,"file":"ast-to-sparql.d.ts","sourceRoot":"","sources":["../../src/core/ast-to-sparql.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,GAAG,EAAE,MAAM,aAAa,CAAC;AAClC,OAAO,EAAE,aAAa,EAAE,QAAQ,EAAE,MAAM,UAAU,CAAC;AAGnD,OAAO,EAAE,WAAW,EAAE,MAAM,gBAAgB,CAAC;AAC7C,OAAO,EAAE,eAAe,EAAE,MAAM,eAAe,CAAC;AAGhD,OAAO,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AACpD,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,OAAO,CAAC;AAGzC,YAAY,EAAE,WAAW,EAAE,CAAC;AAE5B,UAAU,qBAAqB;IAC7B,KAAK,EAAE,QAAQ,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAChC,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,OAAO,CAAC,EAAE,KAAK,CAAC;QAAE,MAAM,EAAE,MAAM,CAAC;QAAC,SAAS,EAAE,KAAK,GAAG,MAAM,CAAA;KAAE,CAAC,CAAC;IAC/D,QAAQ,CAAC,EAAE,OAAO,CAAC;CACpB;AAED,UAAU,eAAe;IACvB,KAAK,EAAE,QAAQ,CAAC;IAChB,IAAI,EAAE,KAAK,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,CAAC;CACtC;AAED;;GAEG;AACH,MAAM,WAAW,oBAAoB;IACnC,aAAa,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,EAAE,CAAC,CAAC;IACvC,iBAAiB,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;IACzC,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB;AAED,qBAAa,oBAAoB;IAiBnB,OAAO,CAAC,MAAM;IAAU,OAAO,CAAC,KAAK,CAAC;IAhBlD,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,iBAAiB,CAAoB;IAC7C,OAAO,CAAC,YAAY,CAAC,CAAuB;IAC5C,OAAO,CAAC,WAAW,CAAc;IACjC,OAAO,CAAC,QAAQ,CASd;gBAEkB,MAAM,EAAE,MAAM,EAAU,KAAK,CAAC,EAAE,MAAM,YAAA,EAAE,WAAW,CAAC,EAAE,WAAW;IAOrF;;OAEG;IACH,gBAAgB,CACd,aAAa,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,EAAE,CAAC,EACtC,iBAAiB,EAAE,GAAG,CAAC,MAAM,EAAE,QAAQ,CAAC,EACxC,OAAO,CAAC,EAAE,MAAM,GACf,IAAI;IAOP,aAAa,CAAC,GAAG,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,EAAE,kBAAkB,UAAO,GAAG,WAAW;IAIlJ,4BAA4B,CAAC,QAAQ,EAAE,cAAc,EAAE,KAAK,EAAE,QAAQ,GAAG,MAAM;IAI/E,iBAAiB,CAAC,IAAI,EAAE,eAAe,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,EAAE,kBAAkB,UAAO,GAAG,WAAW;IAI9H,mBAAmB,CAAC,SAAS,EAAE,qBAAqB,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,WAAW,CAAC,EAAE,MAAM,EAAE,EAAE,kBAAkB,UAAO,GAAG,WAAW;IAI3I,aAAa,CAAC,YAAY,EAAE,KAAK,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,GAAG,eAAe,EAAE,KAAK,CAAC,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,GAAG,WAAW;IAIlI,aAAa,CAAC,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,eAAe,EAAE,cAAc,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,GAAG,WAAW;IAI9J,aAAa,CAAC,eAAe,EAAE,cAAc,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,QAAQ,EAAE,WAAW,CAAC,EAAE,MAAM,GAAG,WAAW;IAI5H,WAAW,IAAI,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC;IAIrC,SAAS,CAAC,MAAM,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,IAAI;IAM5C,2BAA2B,CAAC,MAAM,EAAE,aAAa,GAAG,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,QAAQ,GAAG,MAAM;IAI9G,kBAAkB,CAAC,KAAK,EAAE,OAAO,EAAE,MAAM,CAAC,EAAE,aAAa,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,MAAM,GAAG,MAAM,EAAE;IAIvG,kBAAkB,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAAE,KAAK,EAAE,QAAQ,GAAG,MAAM;IAI5E,eAAe,CAAC,GAAG,EAAE,GAAG,EAAE,MAAM,CAAC,EAAE,QAAQ,GAAG;QAAE,IAAI,EAAE,QAAQ,CAAC;QAAC,OAAO,EAAE,GAAG,CAAC;QAAC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,KAAK,CAAC,CAAA;KAAE;IAS5G,OAAO,CAAC,gBAAgB;CAIzB"}

package/dist/core/ast-to-sparql.js

@@ -26,7 +26,7 @@ class ASTToSPARQLConverter {
         this.expressionBuilder = new expression_builder_1.ExpressionBuilder(this.uriResolver);
     }
     /**
-     * Set table registry for URI reference resolution
+     * Set table registry for URI link resolution
      */
     setTableRegistry(tableRegistry, tableNameRegistry, baseUri) {
         this.tableContext = { tableRegistry, tableNameRegistry, baseUri };