• Remove redundant logQuery() method from QueryBuilder
• Update migration guide with removal details and alternatives
• Enhance query builder docs with SQL inspection examples
• Recommend getSql() and DataSource logging configuration

Remove logQuery method from QueryBuilder

• Removed logQuery() method from QueryBuilder class
• Method delegated to configured logger via getQueryAndParameters()
• Eliminated redundant functionality already provided by automatic query logging

src/query-builder/QueryBuilder.ts

Update migration guide for printSql removal

• Updated section title from "printSql renamed to logQuery" to "printSql removed"
• Clarified that method was redundant due to automatic query logging
• Added code examples showing getSql() / getQueryAndParameters() alternatives
• Added example of enabling query logging via DataSource logging option

docs/docs/guides/8-migration-v1.md

Update query builder docs with SQL inspection guidance

• Replaced logQuery() example with getSql() inspection approach
• Added detailed explanation of getSql(), getQuery(), and getQueryAndParameters() methods
• Added code example showing SQL output with parameter placeholders
• Added section on automatic query logging via DataSource configuration

docs/docs/query-builder/1-select-query-builder.md

Description

The SelectQueryBuilder docs state that getQuery() returns the same SQL string as getSql(), but
getQuery() explicitly returns SQL without parameters being replaced while getSql() returns the
driver-escaped SQL produced via escapeQueryWithParameters(). This can mislead users into using
getQuery() expecting driver-specific placeholders (e.g., $1) and/or the same output as
getSql().

Code

docs/docs/query-builder/1-select-query-builder.md[R815-816]

+`getSql()` returns the SQL with parameter placeholders. `getQuery()` returns the same SQL string. To also see the parameter values, use `getQueryAndParameters()` which returns a `[sql, parameters]` tuple.
+

Evidence

The docs claim getQuery() and getSql() return the same SQL, but the implementation documents and
enforces a semantic difference: getQuery() returns SQL with parameters not replaced, whereas
getSql() is derived from escapeQueryWithParameters(getQuery(), getParameters()).

docs/docs/query-builder/1-select-query-builder.md[801-816]
src/query-builder/SelectQueryBuilder.ts[79-96]
src/query-builder/QueryBuilder.ts[470-488]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs claim `getQuery()` returns the same SQL string as `getSql()`, but in code `getQuery()` is explicitly "without parameters being replaced" while `getSql()` is derived from `escapeQueryWithParameters(getQuery(), getParameters())`.

## Issue Context
This is user-facing documentation in the QueryBuilder guide and can cause confusion when users expect `getQuery()` to show driver-specific placeholders (e.g., `$1`) like `getSql()`.

## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[801-816]
- src/query-builder/SelectQueryBuilder.ts[79-96]
- src/query-builder/QueryBuilder.ts[470-488]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools