[
https://issues.apache.org/jira/browse/IGNITE-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803186#comment-16803186
]
Pavel Kuznetsov commented on IGNITE-11226:
------------------------------------------
1. Done
2. JDBC spec says nothing about prepared statement metadatas (result set and
parameters) that contain multiple sql statements separated by ";" (script).
H2 returns metadata of the first sql statement of the script.
PostgreSql returns all the meta about all the parameters found in the script.
(Thanks for checking)
Mysql doesn't support multiple SELECT statements for the PreparedStatement and
throws parsing error in this case. DML is allowed, returned meta about all the
parameters.
As we discussed, final point:
- result set metadata for the multistatements and dml is null
- parameters metadata about all the parameters of the multistatetment should be
returned.
added implementation notes to the PreparedStatemet implementations.
> SQL: Remove GridQueryIndexing.prepareNativeStatement
> ----------------------------------------------------
>
> Key: IGNITE-11226
> URL: https://issues.apache.org/jira/browse/IGNITE-11226
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Pavel Kuznetsov
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This method is the only leak of H2 internals to the outer code. Close
> analysis of code reveals that the only reason we have it is *JDBC metadata*.
> Need to create a method which will prepare metadata for a statement and
> return it as a detached object. Most probably we already have all necessary
> mechanics. This is more about refactoring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
