Skip to content

Commit e3a305a

Browse files
authored
Merge pull request #86 from itowlson/sqlite-no-close-method-grandad
Remove SQLite `close` method (hangover from v1)
2 parents bf16792 + 6766341 commit e3a305a

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

content/v3/sqlite-api-guide.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,6 @@ The set of operations is common across all SDKs:
3737
|------------|------------|---------|----------|
3838
| `open` | name | connection | Open the database with the specified name. If `name` is the string "default", the default database is opened, provided that the component that was granted access in the component manifest from `spin.toml`. Otherwise, `name` must refer to a store defined and configured in a [runtime configuration file](./dynamic-configuration.md#sqlite-storage-runtime-configuration) supplied with the application.|
3939
| `execute` | connection, sql, parameters | database records | Executes the SQL statement and returns the results of the statement. SELECT statements typically return records or scalars. INSERT, UPDATE, and DELETE statements typically return empty result sets, but may return values in some cases. The `execute` operation recognizes the [SQLite dialect of SQL](https://www.sqlite.org/lang.html). |
40-
| `close` | connection | - | Close the specified `connection`. |
4140

4241
The exact detail of calling these operations from your application depends on your language:
4342

0 commit comments

Comments
 (0)