Documentation Source Text

Check-in [0dc508ed1b]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Comment:One more pass, with a few minor corrections, over the application file format document.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
User & Date: drh 2014-03-15 12:25:31
Fix a hyperlink to the "application file format" page. check-in: 06eecd10f7 user: drh tags: trunk
One more pass, with a few minor corrections, over the application file format document. check-in: 0dc508ed1b user: drh tags: trunk
More edits to the application-file-format document. check-in: c0ac5630f2 user: drh tags: trunk
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/

   287    287   and wrapped pile-of-files formats, both of which usually require a
   288    288   rewrite of the entire document in order to change a single byte.  
   289    289   Pure pile-of-files formats can also
   290    290   do incremental updates to some extent, though the granularity of writes is 
   291    291   usually larger with pile-of-file formats (a single file) than with SQLite
   292    292   (a single page).
   293    293   
   294         -<p>A desktop application built on SQLite can also do continuous update.
   295         -In other words, instead of collecting changes in memory and then writing
          294  +<p>SQLite also supports continuous update.
          295  +Instead of collecting changes in memory and then writing
   296    296   them to disk only on a File/Save action, changes can be written back to
   297         -the disk as they occur.  The avoids loss of work on a system crash or
          297  +the disk as they occur.  This avoids loss of work on a system crash or
   298    298   power failure.  The undo/redo stack can also be kept in the on-disk 
   299    299   database, meaning that undo/redo can occur across session boundaries.
   300    300   Maintenance of the undo/redo stack can often be automated using SQL
   301    301   triggers.
   302    302   
   303    303   <li><p><b>Easily Extensible.</b>
   304    304   As an application grows, new features can be added to an
   358    358   
   359    359   <li><p><b>Multiple Programming Languages.</b>
   360    360   Though SQLite is itself written in ANSI-C, interfaces exist for
   361    361   just about every other programming language you can think of:
   362    362   C++, C#, Objective-C, Java, Tcl, Perl, Python, Ruby, Erlang,
   363    363   JavaScript, and so forth.  So programmers can develop in whatever
   364    364   language they are most comfortable with and which best matches
   365         -the needs of the application.
          365  +the needs of the project.
   366    366   
   367    367   <p>An SQLite application file format is a great 
   368    368   choice in cases where there is a collection or "federation" of
   369    369   separate programs, often written in different languages and by
   370    370   different development teams.
   371    371   This comes up commonly in research or laboratory
   372    372   environments where one team is responsible for data acquisition
   373    373   and other teams are responsible for various stages of analysis.
   374    374   Each team can use whatever hardware, operating system,
   375    375   programming language and development methodology that they are 
   376    376   most comfortable with, and as long as all programs use an SQLite 
   377         -database with a common schema as their application file format, 
   378         -they can all interoperate.
          377  +database with a common schema, they can all interoperate.
   379    378   
   380    379   
   381    380   <li><p><b>Better Applications.</b>
   382    381   If the application file format is an SQLite database, the complete
   383    382   documentation for that file format consists of the database schema,
   384    383   with perhaps a few extra words about what each table and column
   385    384   represents.  The description of a custom file format,