Skip to content

chore(duckdb): add log to ensure duckdb execute init sql and session sql #748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 16, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,7 @@ private void init()
initPool();
if (duckDBSettingSQL != null) {
if (duckDBSettingSQL.getInitSQL() != null) {
LOG.info("Initialize by init SQL"); // Not print the SQL to avoid leaking sensitive information
executeDDL(duckDBSettingSQL.getInitSQL());
}
}
Expand Down Expand Up @@ -123,6 +124,7 @@ private static String buildConnectionInitSql(DuckDBSettingSQL duckDBSettingSQL,
sql.add("SET autoinstall_known_extensions = true");
if (duckDBSettingSQL != null) {
if (duckDBSettingSQL.getSessionSQL() != null) {
LOG.info("Append session SQL to connection init SQL"); // Not print the SQL to avoid leaking sensitive information
sql.add(duckDBSettingSQL.getSessionSQL());
}
}
Expand Down
Loading