|
 |
 |
|
|
|
Litebase 2.23
1. Added a method to get the current slot (LitebaseConnection.getSlot()) being used. Returns -1 except on palm. Now, LitebaseConnection.getSourcePath() won't return the slot passed.
2. Corrected a bug that would throw an exception if the where clause if of the form 1 = 1.
3. PreparedStatement.setNull() now works for blobs.
4. Solved a bug that could make a prepared statement string parameter in a where or having clause cause a strange exception of invalid number.
5. Now possible null values are treated in RowIterator.
Litebase 2.22
1. The table should not be marked as closed properly when throwing a TableNotClosedException if it was not previously closed correctly.
2. The table must be not closed properly in order to recover it.
3. Corrected a small issue that would make a DriverException not to be thrown when creating an index in a non-existing column on Windows 32, Windows CE, Palm OS, iPhone, and Android.
4. The table files must be closed if convert() fails() on Java SE and BlackBerry.
5. The crc was not being calculated correctly for updates.
6. The node count should be reseted when recreating the indices. This could create corrupted indices.
7. .db should be closed if .dbo cannot be openned on desktop and BlackBerry.
8. Corrected a bug that could collect strings and blobs passed to a prepared statement, causing invalid data insertion/update or wrong deletion on Palm, Windows 32, Windows CE, iPhone, and Android.
9. Some string conversions to numerical values could return spourious values if the string range were greater than the type range.
10. Corrected a bug that would possibly not load Litebase native library on Android inside a thread.
Litebase 2.21
1. Solved a problem that could reduce the free memory too much if many prepared statements were created and collected many times.
2. ResultSet.getDateTime(String) could get the wrong column data on Windows 32, Windows CE, iPhone, Palm, and Android.
3. Solved a small bug that could make Litebase crash on Windows 32, Windows CE, Palm, iPhone, and Android when passing 2 arguments to params when issuing a LitebaseConnection.getInstance().
4. Unicode strings were not dealt properly on Windows 32, Windows CE, Palm, iPhone, and Android.
Litebase 2.2
1. Removed unused exception constructors and changed constructors visibility to package because it is not to be used by the user.
2. Added TableNotCreatedException which will be raised whenever a table is not closed properly.
3. Blobs are not loaded anymore in the temporary table when building result sets.
4. Added a crc32 code for every record. Please update your tables.
5. Added a method to recover possible corrupted tables, the ones that were not closed properly.
6. PreparedStatement.setDate() and PreparedStatement.setDateTime() must accept null values on Java and on BlackBerry.
7. Corrected file increasing and shrinking on iPhone.
8. Does not let the table be truncated if an error occurs when loading its metadata.
9. Solved a NPE when using like '%' with a nocase string column on Blackberry and desktop.
10. Now logger and the first driver instantiation can be used safely within different threads ob Windows 32, Windows CE, Palm, and iPhone.
11. Added a method convert() that converts a previous table format to the current one.
12. Drop table was dropping a closed table and all tables starting with the same name of the dropped one.
13. Corrected a bug that would mess data up when purging a table with a big header (more than 512 bytes).
14. Fixed bug in DBListBox. The method setSelectedIndex would not work on a ComboBox initialized with a DBListBox.
15. Now an exception will be raised if one tries to use a prepared statement whose table was dropped after preparing it instead of breaking the application.
16. Now the application will not enter in an infinite loop if an index gets corrupted.
17. Now the rename table will rename the composed indices.
|
|
|
