Using the global `TimeZone` config in the `Properties` object passed to `DriverManager.getConnection` fails with error: "The following options were not recognized: TimeZone"
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with DuckDBDriver.java and DuckDBConnection.java, following the DriverManager.getConnection path into the native startup shown in the stack trace. Compare the Properties handling with DuckDB’s global configuration documentation and reproduce the Scala example using TimeZone. Done means the documented global timezone can be passed through Properties without the unrecognized-option error, with coverage for the connection path.
Written by the indexing model from the issue text.
Description
This error seems counter-intuitive as this config is documented as global: https://duckdb.org/docs/stable/configuration/overview.html#global-configuration-options
Shouldn't this Properties object allow us to configure the global timezone of our statements?
Reproducer (scala code):
val config = new Properties()
config.put("TimeZone", "UTC")
DriverManager.getConnection(url, config).unwrap(classOf[DuckDBConnection])
Error:
java.sql.SQLException: Invalid Input Error: The following options were not recognized: TimeZone
at org.duckdb.DuckDBNative.duckdb_jdbc_startup(Native Method)
at org.duckdb.DuckDBConnection.newConnection(DuckDBConnection.java:62)
at org.duckdb.DuckDBDriver.connect(DuckDBDriver.java:114)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:683)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:191)
...
cc @guizmaii
- Dominant language
- C++
- Stars
- 127
- Forks
- 80
- Avg merge
- 13h 41m
- Merged PRs (30d)
- 44
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from duckdb/duckdb-java
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
duckdb/duckdb-java#832 · 2 comments ·
-
Native SIGSEGV in DuckDB JDBC when repeatedly executing queries with window functions and LIMIT 0 Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-java#871 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
duckdb/duckdb-java#872 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
duckdb/duckdb-java#837 ·
-
executeBatch()` on a prepared INSERT runs s are ~1–2 orders of magnitude slower than the Appender Open
Difficulty 5/5 Over a week Newbie friendliness 42/100
duckdb/duckdb-java#815 · 1 comment ·
All issues in duckdb/duckdb-java
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·