mirror of
https://github.com/sqlite/sqlite.git
synced 2025-08-08 14:02:16 +03:00
Tweaks to the test_intarray documentation and tests.
FossilOrigin-Name: 7107f0dacf4467430d1ca157cb848dde984e48e529e7d67a88b7594b0f8159c9
This commit is contained in:
@@ -13,6 +13,10 @@
|
||||
** This is the C-language interface definition for the "intarray" or
|
||||
** integer array virtual table for SQLite.
|
||||
**
|
||||
** This virtual table is used for internal testing of SQLite only. It is
|
||||
** not recommended for use in production. For a similar virtual table that
|
||||
** is production-ready, see the "carray" virtual table over in ext/misc.
|
||||
**
|
||||
** The intarray virtual table is designed to facilitate using an
|
||||
** array of integers as the right-hand side of an IN operator. So
|
||||
** instead of doing a prepared statement like this:
|
||||
@@ -72,7 +76,10 @@
|
||||
** virtual table is dropped. Since the virtual tables are created in the
|
||||
** TEMP database, they are automatically dropped when the database connection
|
||||
** closes so the application does not normally need to take any special
|
||||
** action to free the intarray objects.
|
||||
** action to free the intarray objects. Because of the way virtual tables
|
||||
** work and the (somewhat goofy) way that the intarray virtual table is
|
||||
** implemented, it is not allowed to invoke sqlite3_intarray_create(D,N,P)
|
||||
** more than once with the same D and N values.
|
||||
*/
|
||||
#include "sqlite3.h"
|
||||
#ifndef SQLITE_INTARRAY_H
|
||||
|
Reference in New Issue
Block a user