Skip to content

fix: use fully qualified name to resolve DuckDB ambiguous reference error #135

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.

Sign up for GitHub

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

Closed
jerome-ng wants to merge 1 commit into from
Closed

fix: use fully qualified name to resolve DuckDB ambiguous reference error #135

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 4 additions & 1 deletion plugins/runtime/edge-runtime/ext/trex/js/dbconnection.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -400,7 +400,10 @@ export class TrexConnection {
`${duckdbNativeSchemName}.COHORT`
);
}*/
const replacement = schemaName === "" ? "" : `${schemaName}.`;
// Use fully qualified 3-part name (catalog.schema.table) to avoid DuckDB
// "Ambiguous reference to catalog or schema" error when databaseCode equals schemaName
const databaseName = this.connection.getdatabase();
const replacement = schemaName === "" ? "" : `${databaseName}.${schemaName}.`;
return sql.replace(/\$\$SCHEMA\$\$./g, replacement);
}
}
Loading