Add en description

This commit is contained in:
adevyatova 2021-08-15 16:34:10 +00:00
parent 346def3666
commit a54060dd02
3 changed files with 32 additions and 37 deletions

View File

@ -5,17 +5,20 @@ toc_title: SQLite
# SQLite {#sqlite}
- What the Database/Table engine does.
- Relations with other engines if they exist.
The engine works with [SQLite](https://www.sqlite.org/index.html).
## Creating a Database {#creating-a-database}
``` sql
CREATE DATABASE ...
CREATE DATABASE sqlite_database
ENGINE = SQLite('db_path')
```
**Engine Parameters**
## Data Types Support {#data_types-support} (for Database engines only)
- `db_path` — Path to SQLite file with the database.
## Data Types Support {#data_types-support}
| EngineName | ClickHouse |
|-----------------------|------------------------------------|
@ -24,11 +27,8 @@ toc_title: SQLite
## Specifics and recommendations {#specifics-and-recommendations}
Algorithms
Specifics of read and write processes
Examples of tasks
Recommendations for usage
Specifics of data storage
SQLite stores the entire database (definitions, tables, indices, and the data itself) as a single cross-platform file on a host machine. It is locking the entire database file during writing. SQLite read operations can be multitasked, though writes can only be performed sequentially.
SQLite does not require service management (such as startup scripts) or access control based on `GRANT` and passwords. Access control is handled by means of file-system permissions given to the database file itself.
## Usage Example {#usage-example}
@ -50,7 +50,3 @@ Result:
```
Follow up with any text to clarify the example.
**See Also**
- [link](#)

View File

@ -5,21 +5,26 @@ toc_title: SQLite
# SQLite {#sqlite}
- What the Database/Table engine does.
- Relations with other engines if they exist.
The engine provide to import and export data to SQLite and query SQLite tables directly in ClickHouse.
## Creating a Table {#creating-a-table}
``` sql
CREATE TABLE ...
CREATE TABLE [IF NOT EXISTS] [db.]table_name
(
name1 [type1],
name2 [type2],
...
)
ENGINE = SQLite('db_path', 'table')
```
**Engine Parameters**
**Query Clauses**
## Virtual columns {#virtual-columns}
List and virtual columns with description, if they exist.
- `name1, name2, ...` — The column names.
- `type1, type2, ...` — The column types.
- `db_path` — Path to SQLite file with the database.
- `table` — The SQLite table name.
## Specifics and recommendations {#specifics-and-recommendations}
@ -52,4 +57,4 @@ Follow up with any text to clarify the example.
**See Also**
- [link](#)
- [The `sqlite` table function](../../../sql-reference/table-functions/sqlite.md)

View File

@ -5,28 +5,22 @@ toc_title: sqlite
## sqlite {#sqlite}
Short description.
Allows to performed queries on data that is stored in the `SQLite` database.
**Syntax**
``` sql
<function syntax>
sqlite('db_path', 'table_name')
```
Alias: `<alias name>`. (Optional)
**Arguments**
More text (Optional).
- `db_path` — Path to SQLite file with the database. [String](../../sql-reference/data-types/string.md).
- `table_name` — The SQLite table name. [String](../../sql-reference/data-types/string.md).
**Arguments** (Optional)
**Returned value**
- `x` — Description. Optional (only for optional arguments). Possible values: <values list>. Default value: <value>. [Type name](relative/path/to/type/dscr.md#type).
- `y` — Description. Optional (only for optional arguments). Possible values: <values list>.Default value: <value>. [Type name](relative/path/to/type/dscr.md#type).
**Returned value(s)**
- Returned values list.
Type: [Type name](relative/path/to/type/dscr.md#type).
- A table object with the same columns as the original `SQLite` table.
**Example**
@ -47,6 +41,6 @@ Result:
``` text
```
**See Also** (Optional)
**See Also**
- [link](#)
- [`SQLite` table engine](../../engines/table-engines/integrations/sqlite.md)