RussellSpitzer commented on code in PR #1802:
URL: https://github.com/apache/polaris/pull/1802#discussion_r2127073797
##########
persistence/relational-jdbc/src/main/java/org/apache/polaris/persistence/relational/jdbc/QueryGenerator.java:
##########
@@ -37,35 +40,51 @@
public class QueryGenerator {
- public static <T> String generateSelectQuery(
+ public static class PreparedQuery {
+ private final String sql;
+ private final List<Object> parameters;
+
+ public PreparedQuery(String sql, List<Object> parameters) {
+ this.sql = sql;
+ this.parameters = parameters;
+ }
+
+ public String getSql() {
+ return sql;
+ }
+
+ public List<Object> getParameters() {
+ return parameters;
+ }
+ }
+
+ public static <T> PreparedQuery generateSelectQuery(
@Nonnull Converter<T> entity, @Nonnull Map<String, Object> whereClause) {
Review Comment:
I'm also on board the static prepared statement bandwagon here (although
maybe not necessarily at compile time). But also agree probably is not required
for this this release. I also think statically defining the prepared statements
but doing that programmatically is also fine. IE, for each class a statement is
defined statically on class initialization but I haven't thought this through.
The key thing would be differentiating between binding of runtime values vs
class entities.
--
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]
