SQLite is a file-based, self-contained database type, which makes it ideal in scenarios where portability and ease of configuration is important. Since SQLite databases are natively supported by MapForce, you do not need to install any drivers to connect to them.
•On Linux, statement execution timeout for SQLite databases is not supported.
•Full text search tables are not supported.
•SQLite allows values of different data types in each row of a given table. All processed values must be compatible with the declared column type; therefore, unexpected values can be retrieved and run-time errors may occur if your SQLite database has row values which are not the same as the declared column type.
•If your mapping should write data to a SQLite database, and if you don't have the target database file already, you will need to create it separately. In this case, you can create it with a tool such as DatabaseSpy or download the SQLite command-line shell from the official website, and create the database file from the command line (see also Example: Mapping data from XML to SQLite). For complete reference to SQLite command syntax, refer to the official SQLite documentation.
•SQLite databases are supported in the MapForce BUILT-IN transformation language (either when you preview the mapping or when you run a MapForce Server execution file).
•SQLite databases are not supported in user-defined functions (UDF).
It is recommended to create tables with the STRICT keyword to ensure more predictable behavior of your data. Otherwise, the data may not be read or written correctly when values of different types are mixed in one column. To find out more about STRICT tables, see the SQLite documentation.