An enum is stored as @Enumerated says (mansart#26) — @Enumerated used to be read and then ignored: every enum was stored by its name, @Enumerated(EnumType.ORDINAL) included. Now @Enumerated(EnumType.ORDINAL), and a bare @Enumerated, store the constant’s index in an integer column, and @Enumerated(EnumType.STRING) stores its name, in writes, row mapping, projections, WHERE bindings and the generated DDL. An enum with no @Enumerated still stores its name, unlike the Jakarta Persistence default, which is the index. This changes what an existing application does if it declares ORDINAL: its tables hold names, and Mansart now writes and reads indexes for that attribute. Either switch the attribute to @Enumerated(EnumType.STRING) (or drop the annotation) to keep the data as it is, or convert the column to indexes before upgrading. Enum storage, Upgrading from 0.3.0.

An UPDATE or a DELETE cannot follow a SELECT clause — the JDQL parser Mansart uses at run time — for a repository generated at run time and for JdqlExecutor.run — read a SELECT clause and then went on to whatever followed it, so SELECT this DELETE FROM Product ran as a DELETE. Such a statement is now refused with a MansartDataException. A tool that tells reads from writes by the first keyword can no longer be led to run a write as a query. @Query JDQL.

mansart-data-cdi is an explicit bean archive (mansart#33) — the jar now ships a META-INF/beans.xml (annotated), like mansart-transactions-cdi, so a CDI container that does not scan implicit archives, such as Weld SE by default, treats it as a bean archive. Under Vauban nothing changes. Bean archives.

EntityModels.of(Class<E>) — the model Mansart uses for an entity: its generated _Entity.$MODEL, or one built at run time from the mapping annotations. A tool no longer has to re-read the annotations or reflect on generated classes to describe an entity. The core API for tools.

JdqlExecutor.run(jdql, parameters, model, runtime) — parses one statement against the entity’s model, binds its named parameters by name, converts a text value to the attribute’s type (enum, java.time, numbers, booleans, UUIDs), and runs it as a @Query method’s statement would, returning a JdqlResult: entities, projected rows, a count or an aggregate’s value. An overload with maxRows reads at most that many rows, as a SQL LIMIT. isWrite and target read a statement’s first keyword and its entity without parsing it. The core API for tools.

An entity model no longer keeps its class loader reachable — models used to be cached in a static map keyed by the entity class, which kept every class and its loader alive. Under a dev reload, where the application layer is replaced while Mansart stays, each discarded layer stayed in memory. Models now live with their class and go away with its loader. The core API for tools.

Mansart JPA P0–P12 delivered within scope — mansart-persistence provides entity lifecycle, JPQL/Criteria, XML mapping, container integration, cache and Validation integration. The locally patched PostgreSQL TCK passes all non-skipped tests; comparative benchmarks and a modular Leyden AOT smoke are recorded. Remaining mapping boundaries and the local TCK patch are explicit; no formal certification or GraalVM native-image support is claimed. See implementation status, TCK evidence and performance methodology.