Support multiple queries in a single statement

未关闭
#277 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
java, sqlite
领域
database

调研方向

Start in CorePreparedStatement, where the issue says the batch array is allocated from the parameter count. Trace how parameter positions are mapped when a prepared statement contains multiple SELECT statements, then inspect nearby tests for prepared statements and multi statement handling. Done means executing the described repeated parameter query no longer throws ArrayIndexOutOfBoundsException.

由索引模型根据 Issue 内容生成。

描述

enhancement:SQLite impacts:JNI

I'm using this JDBC driver in the Apache Incubator Guacamole project, with MyBatis and Guice, to try to make the SQLite database available as an authentication back-end for the product. In a couple of places in the code (1, 2), there are prepared statements passed to the JDBC drivers that contain multiple select statements from different tables, each terminated by a semicolon. This allows the Java code to make a single method call that runs both queries and returns a single result map, and keeps the code simple. It works perfectly fine for MySQL, PostgreSQL, and SQL Server, but generates this ArrayIndexOutOfBoundsException when used with this SQLite JDBC driver.

When the batch array is allocated in the CorePreparedStatement class, it's allocated based on the number of parameters. However, when multiple select statements are used that expect the same parameters to be passed, there will be x * y number of positions, where x is the parameter count and y is the number of SELECT statements, which is what results in the index out of bounds exception.

I'm not sure if batch needs to be dynamically allocated or resized, or if the size that it needs to be can be computed from other available parameters to get the total position count, but the current method does not allow for multiple statements to be prepared properly.

主要语言
Java
星标
3.3k
派生
676
平均合并
1 天 15 小时
30 天内合并 PR
18

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

xerial/sqlite-jdbc 的其他 Issue

查看 xerial/sqlite-jdbc 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。