Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Clarifications and typo fixes in the CSV extension documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
4ca1c49050740c73779d9d4c6bdb6b3b |
| User & Date: | drh 2016-08-08 18:52:53 |
Context
|
2016-08-08
| ||
| 22:40 | Increase the fontsize on the "pi". (check-in: 5933ebb467 user: drh tags: trunk) | |
| 18:52 | Clarifications and typo fixes in the CSV extension documentation. (check-in: 4ca1c49050 user: drh tags: trunk) | |
| 13:48 | Add the sha1 checksum and SQLITE_SOURCE_ID for 3.14 to changes.html. (check-in: 6c613c2c11 user: dan tags: trunk) | |
Changes
Changes to pages/csv.in.
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 |
<p> The first line of the script above causes the [command-line shell] to read and activate the run-time loadable extension for CSV. For an application, the equivalent C-language API is [sqlite3_load_extension()]. Observe that the filename extension (ex: ".dll" or ".so" or ".dylib") is omitted from the extension filename. Omitting the filename extension is not required, but it is help in making the script cross-platform. SQLite will automatically insert the appropriate extension. <p> The second line above creates a virtual table named "t1" that reads the content of the file named in the argument. The number and names of the columns is determined automatically by reading the first line of content. Other options to the CSV virtual table provide the option to take the content from a string rather than a separate file, and give the programmer more control over the number and names of the columns. The options are detailed below. The CSV virtual table is usually created as a TEMP table so that it exists only for the current database connection and does not become a permanent part of the database schema. Note that there is no "CREATE TEMP VIRTUAL TABLE" command in SQLite. Instead, prepend the "temp." schema prefix to the name of the virtual table. |
| | | | |
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 |
<p> The first line of the script above causes the [command-line shell] to read and activate the run-time loadable extension for CSV. For an application, the equivalent C-language API is [sqlite3_load_extension()]. Observe that the filename extension (ex: ".dll" or ".so" or ".dylib") is omitted from the extension filename. Omitting the filename extension is not required, but it helps in making the script cross-platform. SQLite will automatically append the appropriate extension. <p> The second line above creates a virtual table named "t1" that reads the content of the file named in the argument. The number and names of the columns is determined automatically by reading the first line of content. Other options to the CSV virtual table provide the ability to take the CSV content from a string rather than a separate file, and give the programmer more control over the number and names of the columns. The options are detailed below. The CSV virtual table is usually created as a TEMP table so that it exists only for the current database connection and does not become a permanent part of the database schema. Note that there is no "CREATE TEMP VIRTUAL TABLE" command in SQLite. Instead, prepend the "temp." schema prefix to the name of the virtual table. |