You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Lgueg28 The MySQL-specific change was added by #926 . The reason why we don't do the same for other databases is that we haven't received any feedback on the necessity for others.
I just run into an issue with PostgreSQL, which is supposedly related to this. Long story short: I have the sequences table, and ScalikeJDBC's generated "select" query for this table includes sequence_catalog, sequence_schema and other columns from the INFORMATION_SCHEMA.sequences table/view.
(Of course, this needs a separate issue, and I'll create it if I can.)
We are trying to connect to Snowflake and the driver expects a catalog to limit the "show /* JDBC:DatabaseMetaData.getColumns() */ columns" command. Since the getColumns command here https://github.com/scalikejdbc/scalikejdbc/blob/master/scalikejdbc-core/src/main/scala/scalikejdbc/DBConnection.scala#L464 doesn't get a catalog here that results in the command running against the entire database. Is there a reason that catalog is not pulled for non MYSQL databases?
The text was updated successfully, but these errors were encountered: