jdaugherty commented on PR #16631: URL: https://github.com/apache/grails-core/pull/16631#issuecomment-6374258809
Two changes to the branch itself, now a single commit, b429e3794c: - **Renamed to `query-tail`.** With Cypher and MongoDB commands captured alongside SQL, `sql-tail` no longer said what it does. The command is `grails query-tail`, the flag `run-app --query-tail`, the settings `grails.gorm.queryTail.enabled` and `.file`, the capture file `build/query-tail/capture.log`, the packages `org.apache.grails.data.*.querytail`, and the classes `QueryTail*`; the CLI's `SqlStatementType` and `SqlStatementCollapser` became `StatementType` and `StatementCollapser` for the same reason. The guide section, the reference page, the What's New entry and the configuration metadata follow. The PR title and description are updated. - **Squashed.** The fourteen commits are one, so the earlier line-comment anchors point at history that is no longer on the branch; the threads themselves are all resolved. Also in this commit, from a review pass over the Neo4j/MongoDB work: a client-level MongoDB `bulkWrite` now has the keys of its `document` and `updateMods` entries resolved against the mapping like `insert` and `update` do, so a map property's keys cannot leak through it; a capture path that cannot be resolved raises the documented `UncheckedIOException` rather than a sneaky `IOException` through the Java Neo4j factory; the run-app flag, the command description and the configuration metadata describe all three stores; and the connection-source and factory specs of the MongoDB and Hibernate modules gained the query-tail settings and listener lifecycle cases. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
