JDBC driver properties descriptions are missing

[gregsh]

java.sql.Driver#getPropertyInfo returns infos with empty description. (java.sql.DriverPropertyInfo#description)

See https://youtrack.jetbrains.com/issue/DBE-7991

[gotson]

Is this still happening on the latest version?

[gotson]

Description has been there since 2009.

Some properties don't have one, but some do:

open_mode : Database open-mode flag
shared_cache : Enable SQLite Shared-Cache mode, native driver only
enable_load_extension : Enable SQLite load_extension() function, native driver only
cache_size : null
mmap_size : null
case_sensitive_like : null
count_changes : null
default_cache_size : null
defer_foreign_keys : null
empty_result_callback : null
encoding : null
foreign_keys : null
full_column_names : null
fullsync : null
incremental_vacuum : null
journal_mode : null
journal_size_limit : null
legacy_file_format : null
locking_mode : null
page_size : null
max_page_count : null
read_uncommitted : null
recursive_triggers : null
reverse_unordered_selects : null
secure_delete : null
short_column_names : null
synchronous : null
temp_store : null
temp_store_directory : null
user_version : null
application_id : null
limit_length : The maximum size of any string or BLOB or table row, in bytes.
limit_sql_length : The maximum length of an SQL statement, in bytes.
limit_column : The maximum number of columns in a table definition or in the result set of a SELECT or the maximum number of columns in an index or in an ORDER BY or GROUP BY clause.
limit_expr_depth : The maximum depth of the parse tree on any expression.
limit_compound_select : The maximum number of terms in a compound SELECT statement.
limit_vdbe_op : The maximum number of instructions in a virtual machine program used to implement an SQL statement. If sqlite3_prepare_v2() or the equivalent tries to allocate space for more than this many opcodes in a single prepared statement, an SQLITE_NOMEM error is returned.
limit_function_arg : The maximum number of arguments on a function.
limit_attached : The maximum number of attached databases.
limit_like_pattern_length : The maximum length of the pattern argument to the LIKE or GLOB operators.
limit_variable_number : The maximum index number of any parameter in an SQL statement.
limit_trigger_depth : The maximum depth of recursion for triggers.
limit_worker_threads : The maximum number of auxiliary worker threads that a single prepared statement may start.
limit_page_count : The maximum number of pages allowed in a single database file.
transaction_mode : null
date_precision : "seconds": Read and store integer dates as seconds from the Unix Epoch (SQLite standard).
"milliseconds": (DEFAULT) Read and store integer dates as milliseconds from the Unix Epoch (Java standard).
date_class : "integer": (Default) store dates as number of seconds or milliseconds from the Unix Epoch
"text": store dates as a string of text
"real": store dates as Julian Dates
date_string_format : Format to store and retrieve dates stored as text. Defaults to "yyyy-MM-dd HH:mm:ss.SSS"
busy_timeout : null
hexkey_mode : null
password : null
jdbc.explicit_readonly : null

I will add the missing descriptions, but this should already work for some like open_mode, but the screenshot in the attached YouTrack ticket doesn't seem to show that.

@gregsh can you check on your side that it works for the properties with a description ?

[tjlee]

@gotson

Can you check on your side that it works for the properties with a description ?

It works properly for properties with a description:

[github-actions[bot]]

🎉 This issue has been resolved in 3.39.4.0 (Release Notes)