Documentation Source Text

<p> The first argument passed should be the database handle to register the
extension with. The second and third arguments should both be passed 0.

<p> Zipfile is included in most builds of the [command-line shell].

<h1>Using Zipfile</h1>













<p>The zipfile module provides two similar interfaces for accessing zip
archives. A table-valued function, which provides read-only access to
existing archives, and a virtual table interface, which provides both
read and write access.

<h2>Table-Valued Function (read-only access)</h2>
................................................................................
indicate that the entry is a directory or a file.

<p>It is an error to attempt to set the sz or rawdata field to any value
other than NULL. 

<p>The data and method columns may also be set as described for an INSERT
above.  

<p> The first argument passed should be the database handle to register the
extension with. The second and third arguments should both be passed 0.

<p> Zipfile is included in most builds of the [command-line shell].

<h1>Using Zipfile</h1>

<p>The zipfile module provides three similar interfaces for accessing, updating
and creating zip file archives:

<ol>
  <li> A table-valued function, which provides read-only access to existing
       archives, either from the file-system or in-memory.
  <li> A virtual table, which provides read and write access to archives
       stored in the file-system.
  <li> An SQL aggregate function, which can be used to create new archives
       in memory.
</ol>

<p>The zipfile module provides two similar interfaces for accessing zip
archives. A table-valued function, which provides read-only access to
existing archives, and a virtual table interface, which provides both
read and write access.

<h2>Table-Valued Function (read-only access)</h2>
................................................................................
indicate that the entry is a directory or a file.

<p>It is an error to attempt to set the sz or rawdata field to any value
other than NULL. 

<p>The data and method columns may also be set as described for an INSERT
above.  

<h2> The zipfile() Aggregate Function </h2>

<p> New zip archives may be constructed entirely within memory using the
zipfile() aggregate function. Each row visited by the aggregate function
adds an entry to the zip archive. The value returned is a blob containing
the entire archive image.

<p> The zipfile() aggregate function may be called with 2, 4 or 5 
arguments. If it is called with 5 arguments, then the entry added to
the archive is equivalent to inserting the same values into the "name", 
"mode", "mtime", "data" and "method" columns of a zipfile virtual table.

<p> If zipfile() is invoked with 2 arguments, then the entry added to
the archive is equivalent to that added by inserting the same two values into
the "name" and "data" columns of a zipfile virtual table, with all
other values set to NULL. If invoked with 4 arguments, it is equivalent
to inserting the 4 values into the "name", "mode", "mtime" and "data"
columns. In other words, the following pairs of queries are equivalent:

<codeblock>
  SELECT zipfile(name, data) ...
  SELECT zipfile(name, NULL, NULL, data, NULL) ...

  SELECT zipfile(name, mode, mtime, data) ...
  SELECT zipfile(name, mode, mtime, data, NULL) ...
</codeblock>

<p> For example, to create an archive containing two text files, "a.txt" and
"b.txt", containing the text "abc" and "123" respectively:

<codeblock>
  WITH contents(name, data) AS (
    VALUES('a.txt', 'abc') UNION ALL
    VALUES('b.txt', '123')
  )
  SELECT zipfile(name, data) FROM contents;
</codeblock>