Gail Badner I left 4.3 and 4.2 targets but as we discussed these are not simple backports. The gist is the same, but the hooks will be vastly different.

The initial piece is org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentImpl and its determination of org.hibernate.engine.jdbc.env.spi.NameQualifierSupport. It will primarily use whatever Dialect says via Dialect#getNameQualifierSupport. So the first decision point in porting is whether to add that method at all to Dialect. Even in 5.0 that method currently just returns null for all dialects. org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentImpl then looks to DBMD, if available, to make a decision. Specifically it makes a decision based on java.sql.DatabaseMetaData#supportsCatalogsInTableDefinitions and java.sql.DatabaseMetaData#supportsSchemasInTableDefinitions.

From there is where we have lots of divergence, because 4.x has no nice hooks points such as org.hibernate.engine.jdbc.env.spi.QualifiedObjectNameFormatter and org.hibernate.engine.jdbc.env.spi.IdentifierHelper.