[Properties (by Name)] [Methods (by Name)]
SQLite3 itself accepts any column type name and, for a type it does not recognize, stores the data as text
Source position: msesqlite3conn.pas line 84
type tsqlite3connection = class(tcustomsqlconnection,idbcontroller,iblobconnection) |
||
public |
||
constructor create(); override; |
||
function AllocateCursorHandle(); override; |
||
procedure DeAllocateCursorHandle(); override; |
||
procedure preparestatement(); override; |
||
function Fetch(); override; |
||
procedure AddFieldDefs(); override; |
||
procedure UnPrepareStatement(); override; |
||
procedure FreeFldBuffers(); override; |
||
function loadfield(); override; |
||
procedure updateutf8(); override; |
||
function getinsertid(); override; |
||
function fetchblob(); override; |
||
function stringquery(); |
||
function stringsquery(); |
||
property lasterror: Integer; [r] |
||
property lasterrormessage: msestring; [r] |
||
published |
||
property DatabaseName: filenamety; [rw] |
||
property Connected: Boolean; [rw] |
||
property controller: tdbcontroller; [rw] |
||
property options: sqliteoptionsty; [rw] |
||
property busytimeoutms: Integer; [rw] |
|
Since SQLite3 uses file locks for transactions, set busytimeoutms to a positive value |
property Transaction: TSQLTransaction; |
||
property transactionwrite: TSQLTransaction; |
||
property afterconnect: tmsesqlscript; |
||
property beforedisconnect: tmsesqlscript; |
||
end; |
|
SQLite3 itself accepts any column type name and, for a type it does not recognize, stores the data as text |
|
| | | ||
| | | ||
| | | ||
| | | ||
| | | ||
| | | ||
TObject |
SQLite3 itself accepts any column type name and, for a type it does not recognize, stores the data as text; MSEgui only understands a fixed set of SQLite3 type names (mapped to the usual tfield types) — a table declared with an unrecognized type will not work correctly through this connection. Also, since SQLite3 locks the whole database file for a query with an open cursor, leaving a design-time dataset active (fetching) can make the database unusable from a running instance of the application — close design-time datasets before running the project.