- naive @SchemaMapping resolver: 6 statements (5 books/5 authors), 21 statements (20 books/5 authors) - batched @BatchMapping resolver: flat 2 statements in both cases, via DataLoader + .distinct() - dangling authorId nulls the entire GraphQL response via non-null propagation, byte-identical under both resolver strategies - 6-test suite over real HTTP against a live embedded Tomcat instance, SQL captured via a JDK dynamic proxy (StatementLoggingDataSource, reused from sdjpa4-demo) - docs/05: two Boot 4.1 packaging changes hit along the way (DataSourceAutoConfiguration's new package, Jackson 3 by default) - root README: add row for graphql-dataloader; fix openapi-versioning's placeholder link now that post 7477 is live
11 lines
453 B
Plaintext
11 lines
453 B
Plaintext
naive profile / 5 books, 5 distinct authors (no repeats to dedupe)
|
|
|
|
1. select b1_0.id,b1_0.author_id,b1_0.title from book b1_0
|
|
2. select a1_0.id,a1_0.name from author a1_0 where a1_0.id=?
|
|
3. select a1_0.id,a1_0.name from author a1_0 where a1_0.id=?
|
|
4. select a1_0.id,a1_0.name from author a1_0 where a1_0.id=?
|
|
5. select a1_0.id,a1_0.name from author a1_0 where a1_0.id=?
|
|
6. select a1_0.id,a1_0.name from author a1_0 where a1_0.id=?
|
|
|
|
total statements: 6
|