|
 |
 |
|
|
|
Litebase 2.52
1. Corrected a bug with date and datetime using default on JavaSE and Blackberry.
2. Corrected a bug of possible composed index corruption when updating or deleting data.
3. Corrected a possible crash if the path had more than 255 characteres on Windows 32, Windows CE, Palm, Android, iPhone, and iPad.
4. Corrected the fact that a field used in a function can't be fetched using only the name of the field unless it is also in the select field list.
5. Corrected a bug when using a default value of type string which could become messed up on Windows 32, Windows CE, Palm, Android, iPhone, and iPad.
6. Corrected a possible bug when using ResultSetMetaData in tables with more than 128 columns on Windows 32, Windows CE, Palm, Android, iPhone, and iPad.
Litebase 2.51
1. Removed a possible exception when recovering an ascii table with indices on JavaSE and Blackberry.
2. Removed a possible NPE when using indices with null on JavaSE and Blackberry.
Litebase 2.50
1. Corrected a possible crash when doing ordering operations: order by, group by and (re-)creating indices.
2. Corrected a problem of composed indices not returning the expected result.
3. SQLConsole can now be used with ascii tables.
4. Now getInstance() can receive only the parameter chars_type = ...
5. Added LitebaseConnection.isTableProperlyClosed() and LitebaseConnection.listAllTables().
6. Corrected a bug on LitebaseConnection.purge() that could corrupt the table on Windows 32, WindowsCE, Palm, Linux, Android, iPhone, and iPad.
7. Now a select * will cause a SQLParseException if the total number of columns is more than 128 on Palm or 254 on the other platforms.
8. Now the maximum number of columns, fields, tables, etc is 254 instead of 128 except on palm.
9. Added a new sample: LoggerSample. This is to execute a Litebase log file and try to reproduce a problem.
10. Removed some cases when a table was marked as not closed properly without being changed.
|
|
|
