Schema (for schemifier) should be specifiable #49

nafg opened this Issue Aug 13, 2009 · 5 comments


None yet
3 participants

nafg commented Aug 13, 2009

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 ""?


dpp commented Aug 13, 2009

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.


nafg commented Aug 18, 2009

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.


dpp commented Aug 20, 2009

Narrow to broad... that way a global setting can be overridden on an driver-by-driver bases.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment