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
Schemifier seems to decide for you what schema to schemify tables in. When the DriverType doesn't specify a default schema, the username is used. This precludes automatically creating an H2 database with a username because it doesn't have the schema. Should the default schema name for H2 be ""?
The text was updated successfully, but these errors were encountered:
You can now specify schema names either with the DB.globalDefaultSchemaName or alternatively by vending a superconnection from your ConnectionManager (implement newSuperConnection). SuperConnection can have an optional schema name.
Why is the driver type chosen before the global default? Shouldn't it be possible to override any driver that way, not just ones that default to the username?
After all, until now if a DriverType had a schema of Empty, the convention was that it meant to use the username. I'm guessing this is because many drivers to work that way.
Not meant as criticism, just wondering how you see it.
Anyway, thanks for the fix.
Schemifier seems to decide for you what schema to schemify tables in. When the DriverType doesn't specify a default schema, the username is used. This precludes automatically creating an H2 database with a username because it doesn't have the schema. Should the default schema name for H2 be ""?
The text was updated successfully, but these errors were encountered: