Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typo in serverless.html. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
1ac9233c1586d430fe42e07c5ab1a9c2 |
| User & Date: | dan 2009-08-10 11:26:57 |
Context
|
2009-08-10
| ||
| 13:25 | Last minute documentation tweaks before the release of 3.6.17. check-in: 87b76c67f1 user: drh tags: trunk | |
| 11:46 | Fix a few spelling typos. check-in: c3ed16c6d3 user: dan tags: trunk | |
| 11:26 | Fix typo in serverless.html. check-in: 1ac9233c15 user: dan tags: trunk | |
Changes
Changes to pages/serverless.in.
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
<p>
On the other hand, a database engine that uses a server can
provide better protection from bugs in the client
application - stray pointers in a client cannot corrupt memory
on the server.
And because a server is a single persistent process,
it is able control database access with more precision,
allowing for finer grain locking and better concurrancy.
</p>
<p>
Most SQL database engines are client/server based.
Of those that are serverless, SQLite is the only one
known to this author that allows multiple applications
to access the same database at the same time.
</p>
|
| | |
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
<p> On the other hand, a database engine that uses a server can provide better protection from bugs in the client application - stray pointers in a client cannot corrupt memory on the server. And because a server is a single persistent process, it is able to control database access with more precision, allowing for finer grain locking and better concurrency. </p> <p> Most SQL database engines are client/server based. Of those that are serverless, SQLite is the only one known to this author that allows multiple applications to access the same database at the same time. </p> |