The vast majority of database engines run as separate services on a machine and clients communicate with them through a network protocol. SQLite runs in the same process as the host application either as a statically linked or a dynamically loaded library and shares memory space of the client. This provides for a large number of advantages when in-process db is appropriate such as vastly easier integration with he client and almost completely removal of need to marshal data around (certainly not across process boundaries).
For example when running performance analysis of MS SQL server you usually look at both the time it takes to execute any given query as well as the time it takes to transfer the resulting data from server to client. Since SQLite is in-process, the transfer time is essentially zero. You're right about the grammatical error though.. should be "an in-process". The original proposed text on this list was "SQLite is a high-efficiency, in-process, transactional" but "high-efficiency" was dropped without changing "a" to "an". HTH, Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: Dr Gerard Hammond [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 14, 2007 10:33 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Request for help with the SQLite Website The first few words sound incorrect to me. Shouldn't it be. "SQLite is an in-process".... and even then I don't know what 'in-process' actually means. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
