CAST(x AS VARCHAR_IGNORECASE(y) / CHAR(y)) returned a VARCHAR if the new precision was lower than the old precision.

SHUTDOWN DEFAG didn't defragment the database completely if there was a unique hash index for a memory table.

Issue 294: The Maven source bundle now contains a manifest file that allows Eclipse to automatically attach the source code (if Maven is used).

A query with an explicit LIMIT 0 will now return no rows (so far it meant no limit), which is compatible with PostgreSQL and MySQL. A negative limit value (as well as LIMIT NULL) mean no limit (so far a negative limit meant a limit of one row).

A query with an explicit LIMIT 0 will now return no rows (so far it meant no limit), which is compatible with PostgreSQL and MySQL. A negative limit value (as well as LIMIT NULL) mean no limit (so far a negative limit meant a limit of one row).

- Only one space after a period (using two spaces is last century).
- Rename dateClass to dateTimeClass
- Rename *Clazz to *Class
- Use more appropriate method names ("find" for me implies the method might return null)
- Add missing Javadoc comments
- Java field names can end with *Value, but *_value isn't Java style
- Use appropriate variable names ("cn" isn't, "lower" is)
- Use more appropriate method names (getClassForSqlType versus getClassType, createClassName versus convertTableToClassName, createFieldName versus convertColumnToFieldName) 

Lob in database: storing lob objects was not correctly synchronized. This was specially a problem when using Connection.createBlob() / createClob().

Avoid importing java.io.File (the idea is to simplify verifying the file system abstraction is really used everywhere)

Lob in database: storing lob objects was not correctly synchronized. This was specially a problem when using Connection.createBlob() / createClob().