| Feature |
SQLite com |
Sqlite3 com |
Comments |
| Zero Configuration |
Yes |
Yes |
Only the file name of the database file must be supplied. Any other parameters are optional and can be specified at run-time. |
| COM interface |
Integrated |
Integrated |
The database engine and the COM interface are in single DLL. note that axpack1 core is still needed because the output from queries is packed in axpack1 objects. this may sound as added footprint, but in the reality the benefit of using common objects for database communication and other tasks enables the applications to perform very complex tasks with little code. |
| In-Memory Database |
Yes |
Yes |
Opening with empty file name opens a full featured in-memory SQL database .. |
| SQL support |
SQL 92 |
SQL 92 |
Not all the features are supported. See the SQL reference for the both components for details. |
| Sub-queries |
Static |
Full support |
The sub-queries are one of the most powerful mechanisms in SQL. static means that the sub-query is executed once and used for each iteration of the outer query. the full support allows the sub-query to refer fields from the outer query. |
| Query Parameters |
No support, you need a stringutilities object to overcome this. |
Named and by position. |
In SQLite com you can parameterize queries only by using the string formatting functionality supplied by the stringutilities object.
In sqlite3 com you have methods like vexecute, cexecute and aexecute. They allow you put parameters in the executed queries (for example using? Or $ <Name>) and pass values for them as trailing arguments (vexecute), as collection (cexecute) or as array (aexecute ). you can pass any kind of value including binary (BLOB ). |
| Session Parameters |
None |
Scalar and object parameters supported. |
The sqlite3 com's parameters Collection enables the application to set named parameters (values or objects) that can be used in any query executed with this database object. this primary des not only directly executed queries, but also views and triggers. the session parameters are accessible throughParameterDATABASE function. Any method or property on object parameters can be called usingCallobjectDATABASE function. |
| Parameterized views |
No |
Yes |
See session parameters. |
| Ole date/time support |
Yes |
Yes-extended |
For Windows applications it is more convenient to use OLE date/time values which are actually regular Double Precision Floating Point Numbers. this date/time format is better than most other date/time formats (including the date/time format inherited from the SQL standard ). the OLE date/time is not only directly convertible from/to double values, but also precise enough for time stamping. this makes it the recommended date/time format for SQLite COM and sqlite3 COM. |
| Internal database types |
Numeric and text |
Integer, text, real, blob |
In sqlite3 com the internal database value types are enough to fit the needs of any application. |
| Column types |
Smart |
Smart |
SQLite (2 and 3) Allow values of any of the supported types to be put in any column. thus the declared column type is actually just a suggestion. it is up to the application to decide if it will stick to it or will allow mixed types to be put in the column. smart type conversion is applied in the SQL expressions and the application can determine the actual type of the value of each particle field in the returned result. |
| Internal com to database interface |
Textual |
Direct |
In SQLite com the data is automatically or explicitly converted to text before sending/sorting it to/from the Database Engine (Internally ).
In sqlite3 com the data is converted from/to the closest internal database value type which makes the Interface 3 to 5 times faster than in SQLite COM. |
| Triggers |
Yes |
Yes |
|
| Transactions |
Yes |
Yes |
The transactions cannot be nested. |
| Database storage |
Single file (or in-memory) sqlite2 UTF-8 format |
Single file (or in-memory) sqlite3 UTF-8 format. |
The file format is machine independent. for example the Windows CE versions of the SQLite COM/sqlite3 com work with the same files as the desktop versions. the format is the standard SQLite format and is compatible also with non SQLite com implementations based on SQLite (for example UNIX applications using SQLite in their own way) |
| Database Manager |
Phosphatase based |
Phosphatase based |
Database Manager is available for the both components. it is written using phosphatase. it can be obtained separately or as part of other products that include it (if you have installed some of our products you may already have it-check before downloading separately ). |
| Availability |
Windows 95/98/me
Windows NT4/2 k/XP/2003/Vista and above
Windows CE 3.0/CE. NET and above (including Pocket PC and smartphone) |
Windows 95/98/me
Windows NT4/2 k/XP/2003/Vista and above
Windows CE 3.0/CE. NET and above (including Pocket PC and smartphone) |
|
| Database locking |
Yes
(Windows CE-No) |
Yes (page level)
(Windows CE-No) |
On every tops multiple applications can work with the same database file at the same time. on Windows CE devices only one application may have full access to the database while the others can only read from it at the same time. |
| Extending the database with custom functions |
No |
Yes |
See callobject. |
