Skip to content

Commit 0e870ff

Browse files
committed
no-mistakes(document): Updated docs/features/source-kinds.md: derived-field no-read-source rule now notes the projection-reach exception. Other doc surfaces (CONFORMANCE, physical-naming, metamodel-docs, CHANGELOG, naming fixture README) already match the change.
1 parent 5892f85 commit 0e870ff

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

‎docs/features/source-kinds.md‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,10 @@ emitter, two hosts.
9696

9797
A derived field must be **providable** — a read-capable source must be able to carry it. A
9898
derived field on a table-only entity (no read source) is a load error
99-
(`ERR_DERIVED_FIELD_NO_READ_SOURCE`).
99+
(`ERR_DERIVED_FIELD_NO_READ_SOURCE`), with one exception: an `origin.first` or `origin.computed`
100+
that a projection reaches through its `@filter` or a passthrough `@from` is inlined there, so it
101+
needs no read source. The entity's table then gets no column for it: generated entity, DbContext,
102+
Kotlin, Python `ObjectManager` and Java OMDB mappings leave such a field out of table reads and writes.
100103

101104
### Entity read-view vs projection — which to reach for
102105

0 commit comments

Comments
 (0)