Due to a compromise, all users are being forced to change their passwords as a precaution. You will need to use the "Can't access your account?" link next to the Log In button to request a reset email.
We discovered that Informix 10 works well with mapping types "blob" and "clob" if we use our own dialect that's simply derived from the existing Informix dialect by adding the two missing types:
public class Informix10Dialect extends InformixDialect {
public Informix10Dialect() {
super();
registerColumnType( Types.BLOB, "blob" );
registerColumnType( Types.CLOB, "clob" );
}
}
We suggest adding this new dialect to Hibernate Core. (This is similar to issue HHH-2523, but here "clob" is mapped, too.)
We discovered that Informix 10 works well with mapping types "blob" and "clob" if we use our own dialect that's simply derived from the existing Informix dialect by adding the two missing types:
public class Informix10Dialect extends InformixDialect {
public Informix10Dialect() {
super();
registerColumnType( Types.BLOB, "blob" );
registerColumnType( Types.CLOB, "clob" );
}
}
We suggest adding this new dialect to Hibernate Core. (This is similar to issue HHH-2523, but here "clob" is mapped, too.)
1.) Informix 10 has "skip", so now it's possible to implement limixOffset on the database.
2.) when is used "first" in select, it's also useful give hint {+ FIRST_ROWS }, for better performance.
Vladimir Kralik added a comment - 26/May/08 2:48 AM Two new features were added to this patch.
1.) Informix 10 has "skip", so now it's possible to implement limixOffset on the database.
2.) when is used "first" in select, it's also useful give hint {+ FIRST_ROWS }, for better performance.
Improvement
Open
Minor
Two new features were added to this patch.
1.) Informix 10 has "skip", so now it's possible to implement limixOffset on the database.
2.) when is used "first" in select, it's also useful give hint {+ FIRST_ROWS }, for better performance.