|
 |
 |
|
|
|
Litebase 2.02
1. .db should be renamed back in if .dbo rename fails on Windows 32, Windows CE, Palm OS, and iPhone.
2. Corrected a bug that might let Litebase issue an InvalidDateException if a date was inserted in a datetime field on the desktop and BlackBerry.
3. Solved a bug that could cause a GPF or a reset when using composed indices on Windows 32, Windows CE, Palm OS, and iPhone.
4. Removed a possible reset or GPF if there is not enough memory to create the file cache on Windows 32, Windows CE, Palm OS, and iPhone.
5. Removed possible NPE if there is a blank in the beginning of the sql command on the desktop and BlackBerry.
6. A composed index can only be used if all its columns are "ANDED" in the where clause.
7. Corrected a bug that would cause long and double indices to be built incorrectly on Windows 32, Windows CE, Palm OS, and iPhone.
8. Corrected a bug that would cause string indices to be built incorrectly if they had more than one null value on Windows 32, Windows CE, Palm OS, and iPhone.
9. Corrected a bug that would cause indices that have an .idr whose files were erased to be built incorrectly on Windows 32, Windows CE, Palm OS, and iPhone.
10. Corrected a bug that would cause a DriverException if there was a null in an index field when creating it after the table is populated.
11. Corrected a bug that would create a composed index when opening a table using default values on Windows 32, Windows CE, Palm OS, and iPhone.
12. Corrected null values dealing when building an index.
13. .dbo final position must be zeroed when purging all the table on the desktop and BlackBerry.
14. Corrected the simple index re-creation when purging the table on Windows 32, Windows CE, Palm OS, and iPhone.
15. Corrected a bug that would cause a GPF or a reset when logging a prepared statement with a null value on Windows 32, Windows CE, Palm OS, and iPhone.
16. Now prepared statement logging is equal in all platfotms.
17. The composed indices must also be written delayed when setting row increment to a value different to -1.
18. Flushs the files to disk when setting row increment to -1.
19. UPDATE could corrupt .dbo on Windows 32, Windows CE, Palm OS, and iPhone.
20. Corrected a bug that would not create the composed PK correctly with alter table on Windows 32, Windows CE, Palm OS, and iPhone.
21. The strings must always be written at the end of the .dbo. This removes possible bugs when doing updates when using indices. To remove unused .dbo space because of updates in string fields, the purge operation must be done.
22. Fixed Litebase full freezing the device on BlackBerry.
23. Flushs the files imediately to disk when row increment is the default value and rows are being inserted, updated, or deleted.
24. Removed problem with double and long processing when using tables created with Windows 32, Windows CE and desktop on Palm OS.
Litebase 2.01
1. Fixed bug on JDK of tables getting corrupted if the LitebaseConnection is not explicitly closed by the user. (Remember that you should always close the LitebaseConnection at the end of your application, this is just a precaution).
2. Corrected a bug that would let garbage in the number of records parameter in getStrings().
3. If an index is created after populating or purging the table, its nodes will be full in order to improve its usage and search speed.
4. Joins with like were returning the opposite result.
5. The .dbo file must be cropped when closed so that it wont't be too large with zeros at the end.
6. It now deletes the erases the composed index when deleting the whole table.
7. If a single table is being all loaded during a select, sets rowInc to the table's size. This reduces a lot the memory management, making this kind of searches faster.
8. Grows the .dbo file multipling by rowInc instead of 16 if rowInc > 16.
9. Always shrink the .db and .dbo memory files.
10. Non-numerical types don't need to be converted to numbers.
11. Only sets the LitebaseConnection class as finalized if all its objects are finalized when running on the desktop.
12. Corrected a bug that would throw an exception with the message "Incompatible types" when comparing DATE and DATETIME fields.
13. .dbo is now being purged.
14. It is not necessary to save the meta data in the .db for memory tables.
15. The prepared statement parameters for logging must be set as "unfilled" when creating it.
16. When a composed index is deleted, its information is now deleted from the metadata.
17. A NullPointerException could occurr when executing a PreparedStatement when rearanging the nulls of the sql statement.
18. Re-using the record to update the composed index during an update would spoil the subsequent record updates.
19. ResultSet.getStrings() would return an extra-column when doing a select of the form: "select * from table_name".
20. Only grows .dbo if a blob or a string is going to be put after the end of the file.
21. The null columns information must be created before openning the indices when reading the table meta data.
22. The null columns information wasn't being read when re-creating an index.
23. ResultSet.get... methods must be used to get the columns with the same type except for getStrings().
24. Connections stored in method variables can't be closed by gc.
25. Solved some memory leaks.
26. Now there is a LitebaseConnection.getInstance() without parameters. It uses Settings.applicationId.
27. Solved a bug in next() and prev() on the desktop and BlackBerry versions that would happen after doing a delete from table_name.
28. If a table is re-created after the prepared statement is parsed, there won't be a NPE on the desktop and BlackBerry.
29. Solved a bug that would corrupt the indices when deleting the whole table on win32, palm, CE and iPhone.
30. Solved a bug that would happen if a Litebase application doesn't extend MainWindow.
31. LitebaseConnection.getRowCount() will now throw an exception if tableName is null or invalid instead of returning -1.
32. LitebaseConnection.getLogger() and LitebaseConnection.setLogger() are now deprecated. Use the public field instead.
33. When all indices are dropped by the user, the composed primary key can't be deleted.
34. PreparedStatement.setString() for a where clause wouldn't work if the table column wasn't a date, datetime, chars or chars nocase.
35. Litebase would not remove key from the index of the last column.
36. Corrected a bug that would not create a composed primary key properly if it was created using alter table.
Litebase 2.0
» Improved performance using a cache for reading and writing data.
» Improved CE performance using different file creation flags.
» If the table gets corrupted because the .dbo final position could not be saved, an exception will not be thrown anymore. Instead, the size of the .dbo will be used. Some space may be wasted, but no database object will be lost.
» Corrected a bug when renaming files with the same name on CE. Newer devices do not allow this.
» Corrected a bug for tables with many columns, which would corrupt its header.
» Corrected a bug in absolute() and relative() methods from ResultSet, which were not reading null information of the row read.
» Corrected a bug of a blob not being truncated if its size is greater than the column definition.
» Corrected a bug which would corrupt an index if it was very large.
» Now SQLParseException and DriverException can have a cause, which is another exception that caused one of them. This is useful for debugging purposes.
» Corrected a bug that would crash Litebase if the user tried to use a ResultSetMetaData method without creating it.
» Now .idr is only created if it is going to be really used.
» Corrected a bug that would cause a corruption in the simple indices when doing a delete from table without a where clause.
Litebase 2.0 beta 3
» Corrected a bug on joins. Now the tables in the select order may be changed to increase performance. Even so, it is highly recommended that you test different ways of performing a join in order to find the most efficient way to accomplish this operation.
» Corrected a bug when doing purge and rename of a table which would corrupt it.
Litebase 2.0 alfa
» Added support to NULL and DEFAULT values.
» Added support to RESERVED WORDS on Litebase. For more information see LitebaseReservedWords list.
» Improved the parser.
» Added support to simple joins.
» Added support to composed index.
» Added support to composed primary key.
» Added support to blobs.
» Added multiple language support (Portuguese and English).
» Added support to multiple connections.
» Smaller tables (all char types are and blobs have variable size).
» Smaller indexes (all char types are not stored in the indexes).
» Added support to order by for multiple columns.
» Added support to quotes (') inside the strings.
» Removed aspdb support because Litebase2.0 will be used only for TotalCross, which is not supported for PDAs non-NVFS.
» Added new methods to the RowIterator class. With them, it is now possible to get the values of the columns of the current row of the RowIterator object.
» DROP INDEX does not drop primary keys anymore. ALTER TABLE should be used instead.
» Added ResultSet.isNull(int colIndex) and ResultSet.isNull(iString colName). With these methods, it's possible to know if a returned column in a query is null.
» It is now possible to create a simple or a composed primary key with rowid as its member.
» It is now impossible to create a table with repeated column names or use rowid as a column name.
» It is now possible to use date and datetime with like and not like.
» PreparedStatement now has setShort() and setFloat(). They must be used in order to set shorts and floats, respectly. Moreover, it is now IMPOSSIBLE to use a set method for a different type except for setString(), which can be used to set any type except for blobs.
» The table format has changed. The .dbh file is now inside .db. Moreover, blobs and strings are now in a separate file, .dbo (database objects).
|
|
|
