## For SQLite

The following limitations apply to SQLite databases accessed via Libgda:

### Last inserted row's values

The gda_connection_statement_execute_non_select()'s last_insert_row attribute uses the hidden "_ROWID_" column for each table, but it may fail if the table has a column with the same name.

### Date and time

As SQLite stores dates and times as strings, Libgda only handles dates in the format recommended by SQLite, which is "YYYY-MM-DD" for dates, "HH:MM:SS" for times and "YYYY-MM-DD HH:MM:SS" for timestamps (see SQLite's documentation).

### Multi threaded environment

No limitation if sqlite has been compiled with the SQLITE_THREADSAFE=1 flag (which is the case for the embedded version of SQLite). If the system installed SQLite is used and if it was not compiled using that flag, then Libgda sets the SQLite library in a state where multi threading is fully supported.

### Error reporting

If there is not enough free space on the disk which stores an SQLite database, you may have some "Disk I/O error" errors. This is also true for meta data connections which are by default created in a temporary location.