docs(data): query-mechanism decision guide + Spring-Data parity matrix (v26.06.74)#101
Merged
Conversation
…ations matrix + bump v26.06.74 After a full Spring-Data parity audit (CrudRepository/Pageable/derived queries/@query/Specifications/ QBE all present + behavior-tested on relational AND document), added two teaching sections to docs/modules/data.md: 'Choosing a Query Mechanism' (derived vs @query vs Specification vs QBE — when each + when not) and 'Spring Data Parity & Current Limitations' (relational-vs-document capability matrix + explicit list of NOT-yet-implemented Spring features so the docs don't imply false parity). All cited symbols/operators verified against source. Companion plugin skill updated identically (separate repo).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A Spring-Data parity audit confirmed PyFly already implements CrudRepository/PagingRepository, Pageable/Sort/Page, derived queries,
@query, Specifications, and Query-by-Example for BOTH relational and document (all behavior-tested). The docs taught how thoroughly but had almost no when/limits guidance — fixed here.docs/modules/data.mdgains:@queryvs Specifications vs QBE (+ when not to use each), and howPageable/Sortlayer on.@Modifying,Slice, DTO/open projections,StartingWith/IgnoreCase/Top<N>derived keywords) so the docs set honest expectations.The companion plugin's
implement-data-repositoryskill gets the same decision table + matrix + limitations. Every cited symbol/operator verified against source; docs don't claim any unsupported feature. Docs-only change.