Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

move api documentation to wiki

  • Loading branch information...
commit 10e58be62bd1a0c20f7ce2f77d075164e9326e44 1 parent b85af74
@kkaefer kkaefer authored
Showing with 2 additions and 231 deletions.
  1. +2 −231 README.md
View
233 README.md
@@ -6,7 +6,7 @@ node-sqlite3 - Asynchronous, non-blocking [SQLite3](http://sqlite.org/) bindings
# USAGE
-Install with `npm install sqlite3`
+Install with `npm install sqlite3`.
var sqlite3 = require('sqlite3').verbose();
var db = new sqlite3.Database(':memory:');
@@ -30,236 +30,7 @@ Install with `npm install sqlite3`
# API
-`node-sqlite3` has built-in function call serialization and automatically waits before executing a blocking action until no other action is pending. This means that it's safe start calling functions on the database object even if it is not yet fully opened. The `Database#close()` function will wait until all pending queries are completed before closing the database. To control serialization and parallelization of queries, see the *Control Flow* section of this document. For debugging aid, consult the *Error Messages* section.
-
-## new sqlite3.Database(filename, [mode], [callback])
-
-Returns a new Database object and automatically opens the database. There is no separate method to open the database.
-
-* `filename`: Valid values are filenames, `":memory:"` for an anonymous in-memory database and an empty string for an anonymous disk-based database. Anonymous databases are not persisted and when closing the database handle, their contents are lost.
-
-* `mode` *(optional)*: One or more of `sqlite3.OPEN_READONLY`, `sqlite3.OPEN_READWRITE` and `sqlite3.OPEN_CREATE`. The default value is `OPEN_READWRITE | OPEN_CREATE`.
-
-* `callback` *(optional)*: If provided, this function will be called when the database was opened successfully or when an error occurred. The first argument is an error object. When it is `null`, opening succeeded. If no callback is provided and an error occurred, an `error` event with the error object as the only parameter will be emitted on the database object. If opening succeeded, an `open` event with no parameters is emitted, regardless of whether a callback was provided or not.
-
-## Database#run(sql, [param, ...], [callback])
-
-Runs the SQL query with the specified parameters and calls the callback afterwards. It does not retrieve any result data. The function returns the Database object for which it was called to allow for function chaining.
-
-* `sql`: The SQL query to run. If the SQL query is invalid and a callback was passed to the function, it is called with an error object containing the error message from SQLite. If no callback was passed and preparing fails, an `error` event will be emitted on the underlying Statement object.
-
-* `param, ...` *(optional)*: When the SQL statement contains placeholders, you can pass them in here. They will be bound to the statement before it is executed. There are three ways of passing bind parameters: directly in the function's arguments, as an array, and as an object for named parameters.
-
- // Directly in the function arguments.
- db.run("SELECT * FROM tbl WHERE id = ? AND name = ?", 2, "bar");
-
- // As an array.
- db.run("SELECT * FROM tbl WHERE id = ? AND name = ?", [ 2, "bar" ]);
-
- // As an object with named parameters.
- db.run("SELECT * FROM tbl WHERE id = $id AND name = $name", {
- $id: 2,
- $name: "bar"
- });
-
- Named parameters can be prefixed with `:name`, `@name` and `$name`. We recommend using `$name` since JavaScript allows using the dollar sign as a variable name without having to escape it. You can also specify a numeric index after a `?` placeholder. These correspond to the position in the array. Note that placeholder indexes start at 1 in SQLite. `node-sqlite3` maps arrays to start with one so that you don't have to specify an empty value as the first array element (with index 0). You can also use numeric object keys to bind values. Note that in this case, the first index is 1:
-
- db.run("SELECT * FROM tbl WHERE id = $id AND name = ?5", {
- 1: 2,
- 5: "bar"
- });
-
- This binds the first placeholder (`$id`) to `2` and the placeholder with index `5` to `"bar"`. While this is valid in SQLite and `node-sqlite3`, it is not recommended to mix different placeholder types.
-
- If you use an array or an object to bind parameters, it must be the first value in the bind arguments list. If any other object is before it, an error will be thrown. Additional bind parameters after an array or object will be ignored.
-
-* `callback` *(optional)*: If given, it will be called when an error occurs during any step of the statement preparation or execution, *and* after the query was run. If an error occurred, the first (and only) parameter will be an error object containing the error message. If execution was successful, the first parameter is `null`. The context of the function (the `this` object inside the function) is the statement object. Note that it is not possible to run the statement again because it is automatically finalized after running for the first time. Any subsequent attempts to run the statement again will fail.
-
- If execution was successful, it contains two properties named `lastID` and `changes` which contain the value of the last inserted row ID and the number of rows affected by this query respectively. Note that `lastID` **only** contains valid information when the query was a successfully completed `INSERT` statement and `changes` **only** contains valid information when the query was a successfully completed `UPDATE` or `DELETE` statement. In all other cases, the content of these properties is inaccurate and should not be used. The `.run()` function is the only query method that sets these two values; all other query methods such as `.all()` or `.get()` don't retrieve these values.
-
-
-
-## Database#get(sql, [param, ...], [callback])
-
-Runs the SQL query with the specified parameters and calls the callback with the first result row afterwards. The function returns the Database object to allow for function chaining. The parameters are the same as the `Database#run` function, with the following differences:
-
-The signature of the callback is `function(err, row) {}`. If the result set is empty, the second parameter is `undefined`, otherwise it is an object containing the values for the first row. The property names correspond to the column names of the result set. It is impossible to access them by column index; the only supported way is by column name.
-
-
-
-## Database#all(sql, [param, ...], [callback])
-
-Runs the SQL query with the specified parameters and calls the callback with all result rows afterwards. The function returns the Database object to allow for function chaining. The parameters are the same as the `Database#run` function, with the following differences:
-
-The signature of the callback is `function(err, rows) {}`. If the result set is empty, the second parameter is an empty array, otherwise it contains an object for each result row which in turn contains the values of that row, like the `Database#get` function.
-
-Note that it first retrieves all result rows and stores them in memory. For queries that have potentially large result sets, use the `Database#each` function to retrieve all rows or `Database#prepare` followed by multiple `Statement#get` calls to retrieve a previously unknown amount of rows.
-
-
-
-## Database#each(sql, [param, ...], [callback])
-
-Runs the SQL query with the specified parameters and calls the callback with for each result row. The function returns the Database object to allow for function chaining. The parameters are the same as the `Database#run` function, with the following differences:
-
-The signature of the callback is `function(err, row) {}`. If the result set succeeds but is empty, the callback is never called (this will change in the future). In all other cases, the callback is called once for every retrieved row. The order of calls correspond exactly to the order of rows in the result set.
-
-If you know that a query only returns a very limited number of rows, it might be more convenient to use `Database#all` to retrieve all rows at once.
-
-There is currently no way to abort execution.
-
-
-
-## Database#exec(sql, [callback])
-
-Runs all SQL queries in the supplied string. No result rows are retrieved. The function returns the Database object to allow for function chaining. If a query fails, no subsequent statements will be executed (wrap it in a transaction if you want all or none to be executed). When all statements have been executed successfully, or when an error occurs, the callback function is called, with the first parameter being either `null` or an error object. When no callback is provided and an error occurs, an `error` event will be emitted on the database object.
-
-Note: This function will only execute statements up to the first NULL byte. **Comments are not allowed** and will lead to runtime errors.
-
-
-
-## Database#prepare(sql, [param, ...], [callback])
-
-Prepares the SQL statement and optionally binds the specified parameters and calls the callback when done. The function returns a Statement object.
-
-When preparing was successful, the first and only argument to the callback is `null`, otherwise it is the error object. When bind parameters are supplied, they are bound to the prepared statement before calling the callback.
-
-
-
-## Statement#bind([param, ...], [callback])
-
-Binds parameters to the prepared statement and calls the callback when done or when an error occurs. The function returns the Statement object to allow for function chaining. The first and only argument to the callback is `null` when binding was successful, otherwise it is the error object.
-
-Binding parameters with this function completely resets the statement object and row cursor and removes all previously bound parameters, if any.
-
-
-
-## Statement#reset([callback])
-
-Resets the row cursor of the statement and preserves the parameter bindings. Use this function to re-execute the same query with the same bindings. The function returns the Statement object to allow for function chaining. The callback will be called after the reset is complete. This action will never fail and will always return `null` as the first and only callback parameter.
-
-
-
-## Statement#finalize([callback])
-
-Finalizes the statement. This is typically optional, but if you experience long delays before the next query is executed, explicitly finalizing your statement might be necessary. This might be the case when you run an exclusive query (see section *Serialization*). After the statement is finalized, all further function calls on that statement object will throw errors.
-
-
-
-## Statement#run([param, ...], [callback])
-
-Binds parameters and executes the statement. The function returns the Statement object to allow for function chaining.
-
-If you specify bind parameters, they will be bound to the statement before it is executed. Note that the bindings and the row cursor are reset when you specify even a single bind parameter.
-
-The callback behavior is identical to the `Database#run` method with the difference that the statement will not be finalized after it is run. This means you can run it multiple times.
-
-
-
-## Statement#get([param, ...], [callback])
-
-Binds parameters, executes the statement and retrieves the first result row. The function returns the Statement object to allow for function chaining. The parameters are the same as the Statement#run function, with the following differences:
-
-The signature of the callback is `function(err, row) {}`. If the result set is empty, the second parameter is undefined, otherwise it is an object containing the values for the first row. Like with `Statement#run`, the statement will not be finalized after executing this function.
-
-
-
-## Statement#all([param, ...], [callback])
-
-Binds parameters, executes the statement and calls the callback with all result rows. The function returns the Statement object to allow for function chaining. The parameters are the same as the Statement#run function, with the following differences:
-
-The signature of the callback is `function(err, rows) {}`. If the result set is empty, the second parameter is an empty array, otherwise it contains an object for each result row which in turn contains the values of that row. Like with `Statement#run`, the statement will not be finalized after executing this function.
-
-
-
-## Statement#each([param, ...], [callback])
-
-Binds parameters, executes the statement and calls the callback for each result row. The function returns the Statement object to allow for function chaining. The parameters are the same as the Statement#run function, with the following differences:
-
-The signature of the callback is `function(err, row) {}`. If the result set succeeds but is empty, the callback is never called (this will change in the future). In all other cases, the callback is called once for every retrieved row. The order of calls correspond exactly to the order of rows in the result set. Like with `Statement#run`, the statement will not be finalized after executing this function.
-
-If you know that a query only returns a very limited number of rows, it might be more convenient to use `Statement#all` to retrieve all rows at once.
-
-There is currently no way to abort execution.
-
-
-
-# CONTROL FLOW
-
-`node-sqlite3` provides two functions to help controlling the execution flow of statements. The default mode is to execute statements in parallel. However, the `Database#close` method will always run in exclusive mode, meaning it waits until all previous queries have completed and `node-sqlite3` will not run any other queries while a close is pending.
-
-## Database#serialize([callback])
-
-Puts the execution mode into serialized. This means that at most one statement object can execute a query at a time. Other statements wait in a queue until the previous statements executed.
-
-If a callback is provided, it will be called immediately. All database queries scheduled in that callback will be serialized. After the function returns, the database is set back to its original mode again. Calling `Database#serialize()` with in nested functions is safe:
-
- // Queries scheduled here will run in parallel.
-
- db.serialize(function() {
- // Queries scheduled here will be serialized.
- db.serialize(function() {
- // Queries scheduled here will still be serialized.
- });
- // Queries scheduled here will still be serialized.
- });
-
- // Queries scheduled here will run in parallel again.
-
-Note that queries scheduled not *directly* in the callback function are not necessarily serialized:
-
- db.serialize(function() {
- // These two queries will run sequentially.
- db.run("CREATE TABLE foo (num)");
- db.run("INSERT INTO foo VALUES (?)", 1, function() {
- // These queries will run in parallel and the second query will probably
- // fail because the table might not exist yet.
- db.run("CREATE TABLE bar (num)");
- db.run("INSERT INTO bar VALUES (?)", 1);
- });
- });
-
-If you call it without a function parameter, the execution mode setting is sticky and won't change until the next call to `Database#parallelize`.
-
-
-
-## Database#parallelize([callback])
-
-Puts the execution mode into parallelized. This means that queries scheduled will be run in parallel.
-
-If a callback is provided, it will be called immediately. All database queries scheduled in that callback will run parallelized. After the function returns, the database is set back to its original mode again. Calling `Database#parallelize()` with in nested functions is safe:
-
- db.serialize(function() {
- // Queries scheduled here will be serialized.
- db.parallelize(function() {
- // Queries scheduled here will run in parallel.
- });
- // Queries scheduled here will be serialized again.
- });
-
-If you call it without a function parameter, the execution mode setting is sticky and won't change until the next call to `Database#serialize`.
-
-
-
-# ERROR MESSAGES
-
-Writing asynchronous functions using the threadpool unfortunately also removes all stack trace information, making debugging very hard since you only see the error message, not which statement caused it. To mitigate this problem, `node-sqlite3` has a **verbose mode** which captures stack traces when enqueuing queries. To enable this mode, call the `sqlite3.verbose()`, or call it directly when requiring: `var sqlite3 = require('sqlite3').verbose()`.
-
-When you throw an error from a callback passed to any of the database functions, `node-sqlite3` will append the stack trace information from the original call, like this:
-
- Error: SQLITE_RANGE: bind or column index out of range
- --> in Database#run('CREATE TABLE foo (a, b)', 3, [Function])
- at Object.<anonymous> (demo.js:5:4)
- at Module._compile (module.js:374:26)
- at Object..js (module.js:380:10)
- at Module.load (module.js:306:31)
- at Function._load (module.js:272:10)
- at Array.<anonymous> (module.js:393:10)
- at EventEmitter._tickCallback (node.js:108:26)
-
-Note that you shouldn't enable the verbose mode in a production setting as the performance penalty for collecting stack traces is quite high.
-
-Verbose mode currently does not add stack trace information to error objects emitted on Statement or Database objects.
-
+See the [API documentation](https://github.com/developmentseed/node-sqlite3/wiki) in the wiki.
# BUILDING
Please sign in to comment.
Something went wrong with that request. Please try again.