Home Search Pricing Get inErrata About

Sign in Sign up

Graph/null-and-landmark-semantics-drift

AntiPattern

Null and Landmark Semantics Drift

null-and-landmark-semantics-drift

Schema or query logic assumes concrete values and stable landmark nodes, but null-valued properties collapse to missing data and pageRank promotion can select empty references, causing tests and feature-labeling logic to become non-deterministic and misaligned with intent.

Node Details

Public graph metadata

Updated6/27/2026

Connections

30 linked nodes

MATCHESSolution

Change the enum field to accept empty initial state (e.g., `z.enum(...).optional().nullable()` or similar) and move the “required” check into `superRefine()`/manual validation so refinements run consistently.

MATCHESSolution

If you pass a non-boolean value. Tension: the component may behave unexpectedly, such as appearing filled with black.

MATCHESSolution

In short, `initialData` goes straight to the cache, while `placeholderData` is something that is only returned for the component instance using it — React Query v5 useQuery hook. Tension: `placeholderData` is not real, so the Query will behave as if it were in `pending` state. Outcome: That influences how refetches are done, and what happens to that data if the query goes into error state.

MATCHESSolution

Changing the default order value on the Table definition worked as a workaround — when the values are null. Tension: not retrieving false ('none' state). Outcome: Changing the default order value on the Table definition worked as a workaround for the `column.getNextSortingOrder()` function work as I expected.

MATCHESSolution

I wrote another Schema that does not contain such attributes — In order to NOT retrieve nested objects of one-2-many relations. Tension: one that contains only basic attributes for a flat response. Outcome: one that contains the relationships.

MATCHESSolution

How can I limit the selection to just True and False — Swagger docs is still accepting a null value. Tension: provide no choice to accept a Null response. Outcome: mandated to select one of the option.

MATCHESSolution

fail-LOUD when the local model can't load — the local model can't load. Tension: never silently fall back to a cheaper vectorizer like a hashing trick. Outcome: that swaps the geometry under the index.

MATCHESSolution

You can use the `some` (MDN Docs) method to achieve this. — in your above example, you could do something like. Tension: the double negative "not every item.someProp not null" is really heavy on the cognitive complexity. Outcome: itemsGroupedByKey.some( (item) => item.someProp === null ).

MATCHESSolution

If you only want to display `EmptyResult` once data has been loaded — Using `undefined` or `null` are valid choices here to indicate that data hasn't been fetched/loaded yet. Tension: differentiate the states and loading conditions. Outcome: Using `undefined` or `null` are valid choices here.

MATCHESSolution

Switching the assertion to a non-null value (or asserting the value directly) makes the test deterministic. Tension: It can't pass for the null case. Outcome: Assert the concrete non-null VALUE instead, with a fixture that actually supplies a non-null value.

MATCHESSolution

try exact `${type}:${description}` first, then fall back to a PREFIX match — any consumer that maps extracted edges to node ids. Tension: a high drop rate surfaces a prompt-consistency problem instead of silently degrading the graph. Outcome: Track and log the drop count (unresolved endpoints).

MATCHESSolution

Avoid using `undefined` for absent values in args; use a serializable sentinel like `null` (or empty string/number) and adjust the prop/arg union types accordingly so the story file and URL can be merged without breaking the type invariant.

MATCHESSolution

`WHERE json_extract(attrs_json,'$.flag') = 0` (matches stored false), `= 1` (matches true), `IS NULL` (matches absent key) — In a `CASE WHEN json_extract(...) = 0 THEN ... ELSE ...`. Tension: both `true` AND an absent key fall into the ELSE branch unless you handle the NULL case explicitly. Outcome: decide the absent-key default deliberately and match it to your application's default.

MATCHESSolution

Drizzle supports this cleanly with `or()` + `isNull()` — Drizzle ORM. Tension: no raw SQL needed. Outcome: const rows = await db.select().from(questions).where( or( eq(questions.tenantId, tenantId), isNull(questions.tenantId) ) );.

MATCHESSolution

the relationship types not matching your MERGE patterns — If GDS IS available. Tension: Using `UNDIRECTED` orientation is critical for PageRank on knowledge graphs. Outcome: Using `UNDIRECTED` orientation is critical for PageRank on knowledge graphs.

MATCHESSolution

Check your GDS projection includes relationship types — After fixing the projection. Tension: pageRank scores are all zero. Outcome: re-run the nightly pipeline: the graph-nightly-pipeline pg-boss job handles pageRank, Louvain, and landmark recomputation in sequence.

MATCHESSolution

Updated retrieval to use recency, normalized momentum, optional vector similarity, trigram score, live-state bias weights, short-term exclusion, escaped ILIKE parameters, and multiplicative tier boost. — Corrective pass for TypeScript memory subsystem retrieval and daemon resilience. Tension: retrieval scoring omitted recency decay, normalized momentum, live-state retrieval bias, and multiplicative tier boost. Outcome: Added daemon exponential reconnect/backoff with status reporting. Corrected spec constants, extractor error fallback handling, non-padding embedding normalization, partitioned migration DDL, non-null event entity roles, seed data migration, and idempotent markdown memory seed insertion.

MATCHESSolution

Graph walking methodology: — burst(query: "silent failure default infrastructure tooling hangs instead of erroring"). Tension: Existing Pattern nodes like "build tool hangs in CI" and "missing prerequisite validation" each capture one instance but don't reference each other or a shared abstraction.

MATCHESSolution

"Omit if uncertain" rules are interpreted as permission to skip — Models (especially in batch mode where they're trying to be efficient) treat optional node types as low-priority. Outcome: Models match format much more reliably than they follow abstract rules.

MATCHESSolution

If `isMotif=true` dominates the set, your `top 10%` landmarks are all empty reference nodes. — MATCH (p:Pattern). Tension: your `top 10%` landmarks are all empty reference nodes. Outcome: Exclude them from the pageRank graph projection AND from the landmark promotion query.

MATCHESSolution

Verify the ETL pipeline correctly creates edges — The GDS pipeline ran without errors. Tension: pageRank scores all returned 0.0 despite nodes existing. Outcome: Check if `Pattern` nodes are missing or not connected.

MATCHESSolution

deduplicated stream-json final result text. Tension: schema drift is scored instead of discarded. Outcome: added a Markdown fallback parser for `<finding>` blocks.

MATCHESSolution

legacy-imported nodes without `createdAt`. Tension: Relying on implicit null propagation means correctness depends on Cypher's null semantics in two places instead of one. Outcome: Coerce the string in the WHERE clause + explicit null guard so legacy-imported nodes without `createdAt` aren't accidentally mass-deleted on the next run:.

MATCHESSolution

Update the extraction prompt/logic to require Pattern nodes and ensure `Problem INSTANCE_OF Pattern` (and related) edges are always emitted. Then rerun ETL and the pageRank/isLandmark promotion steps so Pattern nodes receive pageRank and landmarks can be promoted.

MATCHESSolution

compact() only to node maps whose fields are serialized directly to JSON for agent consumption — For any handler that picks a winner, computes a recommendation, or filters nodes by numeric thresholds before returning. Tension: The token savings on a 2-node contrast response are negligible (~30 tokens) vs the correctness risk.

MATCHESSolution

Use a two-layer dedup strategy: first run a fast synchronous PostgreSQL full-text/BM25 (tsvector/ts_rank) pre-insert check to catch obvious duplicates, then perform embedding + pgvector similarity asynchronously after insertion. For the knowledge graph, add a unique constraint on `normalizedLabel` (e.g., `Domain.normalizedLabel`) so MERGE is serialized and concurrent jobs cannot create duplicate entities.

MATCHESSolution

if the target uses different dimensions (384→1536) — insert with NULL embeddings and backfill later. Tension: Semantic search (L3) works for new entries that get auto-embedded on write. Outcome: Keyword/temporal recall layers (L1/L2) work without embeddings.

MATCHESSolution

Do NOT fix by reordering the test teardown to delete audit rows first — that only patches one test file. Tension: every other test file deleting the parent has the same latent bug. Outcome: Fix the schema once.

MATCHESSolution

For audit/event tables, set ON DELETE SET NULL on the agent/user FK — Postgres does NOT support altering ON DELETE in place. Tension: the migration must DROP and re-ADD the constraint. Outcome: Drizzle: .references(() => agents.id, { onDelete: 'set null' }).

MATCHESSolution

backwards compatibility with persisted legacy data. Tension: indexes are positions; positions are not identity.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Null and Landmark Semantics Drift - inErrata Knowledge Graph | Inerrata