|
 |
 |
|
|
|
Litebase 2.14
1. Relative paths can't be used with Litebase. An exception will be thrown on all platforms if a relative path is used to open a connection with
Litebase either using dataPath or passing a path to getInstance().
2. Corrected a bug that could crash the application when using logger on Windows 32, Windows CE, Palm OS, and iPhone.
3. Using setDateTime(time) would store a wrong second value on Windows 32, Windows CE, Palm OS, and iPhone.
4. Now removes not boolean operator from expression trees so that indices can be used in more situations.
5. Must trim ascii strings if they are longer than the field size definition on Java and on BlackBerry.
6. Must trim strings during index update if they are longer than the field size definition on Windows 32, Windows CE, Palm OS, and iPhone.
7. Must free Litebase when closing the connection even if the log string creation fails on Windows 32, Windows CE, Palm OS, and iPhone.
8. Corrected a buffer overflow when using logger on Windows 32, Windows CE, Palm OS, and iPhone.
9. Index creation for date types could create corrupted indices.
Litebase 2.13
1. Changed the way a tree with ORs is built in order to speed up queries with indices.
2. Corrected a bug that could make joins not work with ORs using indices.
3. If the table to be sorted had just one row, the selection of a random pivot could lead to an access to an inexistent second row.
4. rowid was not being returned correctly if the select used the table fields order beggining with rowid on Windows CE, Windows 32, Palm, and iPhone.
5. Now a DriverException is thrown instead of returning an invalid value when using an invalid column index in ResultSetMetaData methods.
6. Current rowid was not being corrected fetched from the table when re-opening it.
7. Corrected a bug that could make an identifier with digits colide with keywords during the parsing process.
8. The index node count was not being loaded when loading the indices, which could cause an infinite loop when using them on Eclipse and BlackBerry.
Litebase 2.12
1. Corrected prepared statement parsing for create index.
2. DATETIME indices would be recreated incorrectly on desktop and BlackBerry.
3. guich: When creating indices, we now check if the records are already sorted and skip the sort. Also removed recursion from qsort algorithm, what makes possible to order huge tables. Now index resorting has a limited time of (LitebaseConnection.indexSortMaxTime = 20 if JavaSE else 40) seconds; if it takes more than that, the sort stops, resulting in a bigger index file.
4. If the select fields are in the table order beginning with rowid, do not build a temporary table.
5. Corrected a bug that would crash the program when issuing ResultSet.getChars() with a select which does not use a temporary table on Windows 32, Windows CE, Palm, and iPhone.
6. guich: Fixed "ArrayIndexOutOfBoundsException" at desktop/blackberry when trying to get a column with invalid index from a resultset.
7. The size of the string or blob must be taken into consideration when growing the memory or disk file because it can be zero, and this size is used to calculate the file growing. This would happen only on desktop and Blackberry.
8. When reading a file, an exception must not be thrown when reading zero bytes on desktop and BlackBerry.
Litebase 2.11
1. LitebaseConnection.language is now a public field. It must be accessed directly. LitebaseConnection.getLanguage() and LitebaseConnection.setLanguage() do not exist anymore.
2. Corrected a possible .idr corruption if it was used after a LitebaseConnection.closeAll().
3. The string matrix size can't take into consideration rows that are before the result set pointer in ResultSet.getStrings().
4. Solved bugs with result set dealing when not using temporary tables with deleted rows.
5. Solved a bug with joins which could return more answers than desired when the join uses indices.
Litebase 2.1
1. select * from table_name does not create a temporary table anymore. If the table is altered while holding a result set, the result set WILL BE CHANGED!
2. Now Litebase supports tables with ascii strings.
3. LitebaseConnection.getLogger() and LitebaseConnection.setLogger() are no longer deprecated. They are necessary if the logger is used within threads
4. Corrected a bug that could corrupt the table when updating the composed index.
5. Removed memory leaks concerning blobs.
6. Removed problem with long processing.
7. Logger in prepared statement could crash Litebase because it was losing its executing path.
8. Corrected a bug that would corrupt a date time inserted in a prepared statement on Windows 32, Windows CE, Palm and iPhone.
9. Corrected a bug that could re-create simple indices with wrong properties after a delete in the whole table on Windows 32, Windows CE, Palm and iPhone.
2.1a
10. Corrected a bug that could cause a connection to be not found because of a hash miscalculation of the application id on Windows 32, Windows CE, Palm and iPhone.
11. Fixed a problem that could crop data from database indices on desktop and BlackBerry.
12. Corrected wrong comparison order when using composed indices on desktop and BlackBerry.
|
|
|
