diff --git a/docs/docusaurus/src/components/AlternatingFeatures/styles.module.css b/docs/docusaurus/src/components/AlternatingFeatures/styles.module.css index 32ac32e2bd..dfc0bbf77c 100644 --- a/docs/docusaurus/src/components/AlternatingFeatures/styles.module.css +++ b/docs/docusaurus/src/components/AlternatingFeatures/styles.module.css @@ -16,7 +16,7 @@ .featureImageWrapper { flex: 1; min-width: 200px; - height: 200px; + min-height: 200px; display: flex; align-items: center; /* Выравнивание по вертикали */ justify-content: center; /* Выравнивание по горизонтали */ diff --git a/docs/docusaurus/src/pages/index.module.css b/docs/docusaurus/src/pages/index.module.css index 39c2d7bb3f..3bb1cbd4d2 100644 --- a/docs/docusaurus/src/pages/index.module.css +++ b/docs/docusaurus/src/pages/index.module.css @@ -53,6 +53,7 @@ align-items: left; justify-content: ltft; margin-left: -10px; + flex-wrap: wrap; } .button{ diff --git a/docs/en/md/Instructions/MSSQL.md b/docs/en/md/Instructions/MSSQL.md index 152a86ac88..e860c241df 100644 --- a/docs/en/md/Instructions/MSSQL.md +++ b/docs/en/md/Instructions/MSSQL.md @@ -35,7 +35,8 @@ By default, all SELECT queries return an array of selected data, while other que The library supports operation in TLS mode. To enable it, you need to configure TLS settings using the `GetTlsSettings` function and pass them as the corresponding parameter to the `CreateConnection` function or one of the ORM functions that support this parameter. If the TLS parameter is not provided when calling these functions, the connection will be initialized in an unsecured mode. :::tip -TLS settings can only be applied when the connection is established — either explicitly when using the `CreateConnection` function or implicitly when passing a connection string to ORM methods. Providing TLS settings along with an already established connection (passed via the *Connection* parameter) will be ignored. ::: +TLS settings can only be applied when the connection is established — either explicitly when using the `CreateConnection` function or implicitly when passing a connection string to ORM methods. Providing TLS settings along with an already established connection (passed via the *Connection* parameter) will be ignored. +::: ## Compatibility diff --git a/docs/en/md/Instructions/MySQL.md b/docs/en/md/Instructions/MySQL.md index a33852bac6..9846aa5007 100644 --- a/docs/en/md/Instructions/MySQL.md +++ b/docs/en/md/Instructions/MySQL.md @@ -54,7 +54,8 @@ The MySQL connector supports the use of positional parameters. All values passed The library supports operation in TLS mode. To enable it, you need to configure TLS settings using the `GetTlsSettings` function and pass them as the corresponding parameter to the `CreateConnection` function or one of the ORM functions that support this parameter. If the TLS parameter is not provided when calling these functions, the connection will be initialized in an unsecured mode. :::tip -TLS settings can only be applied when the connection is established — either explicitly when using the `CreateConnection` function or implicitly when passing a connection string to ORM methods. Providing TLS settings along with an already established connection (passed via the *Connection* parameter) will be ignored. ::: +TLS settings can only be applied when the connection is established — either explicitly when using the `CreateConnection` function or implicitly when passing a connection string to ORM methods. Providing TLS settings along with an already established connection (passed via the *Connection* parameter) will be ignored. +::: ## Compatibility diff --git a/docs/en/md/Instructions/PostgreSQL.md b/docs/en/md/Instructions/PostgreSQL.md index 9231bed15b..e590fd117a 100644 --- a/docs/en/md/Instructions/PostgreSQL.md +++ b/docs/en/md/Instructions/PostgreSQL.md @@ -1,84 +1,85 @@ ---- -id: PostgreSQL -sidebar_class_name: PostgreSQL ---- - - - -# PostgreSQL - -This section is dedicated to the PostgreSQL database library. On this page, all the steps necessary to start working are described - -
- - -
An external component is used to implement some functions in this library
-Please review the ["About external components"](/docs/Start/Component-requirements) section before getting started
-
- - -
- - -
This library requires **OpenSSL 3.x** to run on Linux
-Learn more: "Using OpenSSL in External Components"
-
- -## About implemented methods - -This library has two parts: basic methods, like connecting and executing SQL queries, and a small ORM for common operations like CREATE, SELECT, INSERT, DELETE, and so on. Working through the ORM and through the query texts executed through the `ExecuteSQLQuery()` function is technically the same: the ORM simply generates the SQL query text based on the layouts, but then also calls them through this function - -By default, all SELECT queries return an array of selected data, while other queries return only `true` in the `result` field on success, or `false` and error text in the `result` and `error` fields, respectively. To execute queries that require data to be returned but are not SELECT queries, the `ExecuteSQLQuery()` function has a `ForceResult` parameter - -## Query parameters - -The PostgreSQL connector supports the use of positional parameters. All values passed both when executing queries directly through the `ExecuteRequestSQL()` function and in ORM methods with value setting, such as `AddRecords` and `UpdateRecords`, must be a structure of the form `{'Data Type': 'Value'}`. The following data types are supported: - -:::TIP -🟢 - Implemented, tested; 🟡 - Implemented, not tested -::: - - | Type | Support | Synonym | Native types| - |-|-|-|-| - | BOOL | 🟢 | - | Bool | - | "char" | 🟢 | OLDCHAR | Number | - | SMALLINT | 🟢 | - | Number | - | SMALLSERIAL | 🟢 | - | Number | - | INT | 🟢 | - | Number | - | SERIAL | 🟢 | - | Number | - | BIGINT | 🟢 | - | Number | - | BIGSERIAL | 🟢 | - | Number | - | OID | 🟢 | - | Number | - | REAL | 🟢 | - | Number | - | DOUBLE PRECISION | 🟢 | DOUBLE_PRECISION | Number | - | VARCHAR | 🟢 | - | String | - | TEXT | 🟢 | - | String | - | CHAR | 🟢 | - | String | - | CITEXT | 🟢 | - | String | - | NAME | 🟢 | - | String | - | INET | 🟢 | - | String | - | UUID | 🟢 | - | String, УникальныйИдентификатор | - | TIMESTAMP | 🟢 | - | Date, String (ISO 8601, RFC 3339) | - | TIMESTAMP WITH TIME ZONE | 🟢 | TIMESTAMP_WITH_TIME_ZONE | Date (the time zone will be specified as UTC), String (RFC 3339) | - | DATE | 🟢 | - | Date (any time part), String (ISO 8601, RFC 3339) | - | TIME | 🟢 | - | Date (any date part), String (ISO 8601, RFC 3339) | - | BYTEA | 🟢 | - | BinaryData, File path, Base64 String (all converted to a Base64 string) | - | JSON | 🟢 | - | Array, Structure, Map, String (JSON) | - | JSONB | 🟢 | - | Array, Structure, Map, String (JSON) | - | LTREE | 🟡 | - | String | - | LQUERY | 🟡 | - | String | - | LTXTQUERY | 🟡 | - | String | - | HSTORE | 🟡 | - | Structure, Map | - -A similar list of types is also available to retrieve as query results from PostgreSQL - -## TLS - -The library supports operation in TLS mode. To enable it, you need to configure TLS settings using the `GetTlsSettings` function and pass them as the corresponding parameter to the `CreateConnection` function or one of the ORM functions that support this parameter. If the TLS parameter is not provided when calling these functions, the connection will be initialized in an unsecured mode. - -:::tip -TLS settings can only be applied when the connection is established — either explicitly when using the `CreateConnection` function or implicitly when passing a connection string to ORM methods. Providing TLS settings along with an already established connection (passed via the *Connection* parameter) will be ignored. ::: - -## Compatibility - +--- +id: PostgreSQL +sidebar_class_name: PostgreSQL +--- + + + +# PostgreSQL + +This section is dedicated to the PostgreSQL database library. On this page, all the steps necessary to start working are described + +
+ + +
An external component is used to implement some functions in this library
+Please review the ["About external components"](/docs/Start/Component-requirements) section before getting started
+
+ + +
+ + +
This library requires **OpenSSL 3.x** to run on Linux
+Learn more: "Using OpenSSL in External Components"
+
+ +## About implemented methods + +This library has two parts: basic methods, like connecting and executing SQL queries, and a small ORM for common operations like CREATE, SELECT, INSERT, DELETE, and so on. Working through the ORM and through the query texts executed through the `ExecuteSQLQuery()` function is technically the same: the ORM simply generates the SQL query text based on the layouts, but then also calls them through this function + +By default, all SELECT queries return an array of selected data, while other queries return only `true` in the `result` field on success, or `false` and error text in the `result` and `error` fields, respectively. To execute queries that require data to be returned but are not SELECT queries, the `ExecuteSQLQuery()` function has a `ForceResult` parameter + +## Query parameters + +The PostgreSQL connector supports the use of positional parameters. All values passed both when executing queries directly through the `ExecuteRequestSQL()` function and in ORM methods with value setting, such as `AddRecords` and `UpdateRecords`, must be a structure of the form `{'Data Type': 'Value'}`. The following data types are supported: + +:::TIP +🟢 - Implemented, tested; 🟡 - Implemented, not tested +::: + + | Type | Support | Synonym | Native types| + |-|-|-|-| + | BOOL | 🟢 | - | Bool | + | "char" | 🟢 | OLDCHAR | Number | + | SMALLINT | 🟢 | - | Number | + | SMALLSERIAL | 🟢 | - | Number | + | INT | 🟢 | - | Number | + | SERIAL | 🟢 | - | Number | + | BIGINT | 🟢 | - | Number | + | BIGSERIAL | 🟢 | - | Number | + | OID | 🟢 | - | Number | + | REAL | 🟢 | - | Number | + | DOUBLE PRECISION | 🟢 | DOUBLE_PRECISION | Number | + | VARCHAR | 🟢 | - | String | + | TEXT | 🟢 | - | String | + | CHAR | 🟢 | - | String | + | CITEXT | 🟢 | - | String | + | NAME | 🟢 | - | String | + | INET | 🟢 | - | String | + | UUID | 🟢 | - | String, УникальныйИдентификатор | + | TIMESTAMP | 🟢 | - | Date, String (ISO 8601, RFC 3339) | + | TIMESTAMP WITH TIME ZONE | 🟢 | TIMESTAMP_WITH_TIME_ZONE | Date (the time zone will be specified as UTC), String (RFC 3339) | + | DATE | 🟢 | - | Date (any time part), String (ISO 8601, RFC 3339) | + | TIME | 🟢 | - | Date (any date part), String (ISO 8601, RFC 3339) | + | BYTEA | 🟢 | - | BinaryData, File path, Base64 String (all converted to a Base64 string) | + | JSON | 🟢 | - | Array, Structure, Map, String (JSON) | + | JSONB | 🟢 | - | Array, Structure, Map, String (JSON) | + | LTREE | 🟡 | - | String | + | LQUERY | 🟡 | - | String | + | LTXTQUERY | 🟡 | - | String | + | HSTORE | 🟡 | - | Structure, Map | + +A similar list of types is also available to retrieve as query results from PostgreSQL + +## TLS + +The library supports operation in TLS mode. To enable it, you need to configure TLS settings using the `GetTlsSettings` function and pass them as the corresponding parameter to the `CreateConnection` function or one of the ORM functions that support this parameter. If the TLS parameter is not provided when calling these functions, the connection will be initialized in an unsecured mode. + +:::tip +TLS settings can only be applied when the connection is established — either explicitly when using the `CreateConnection` function or implicitly when passing a connection string to ORM methods. Providing TLS settings along with an already established connection (passed via the *Connection* parameter) will be ignored. +::: + +## Compatibility + Technically, the client implementation is a Native component in Rust. It comes in a zip archive format, and, in theory, should work on all available platforms: x86 and x64 Windows and Linux. The actual testing was done on Windows x64 and, cossentially (via OneScript), on Linux x64 \ No newline at end of file diff --git a/docs/en/md/Instructions/SQLite.md b/docs/en/md/Instructions/SQLite.md index 82f964faa5..fee90a94e4 100644 --- a/docs/en/md/Instructions/SQLite.md +++ b/docs/en/md/Instructions/SQLite.md @@ -1,31 +1,31 @@ ---- -id: SQLite -sidebar_class_name: SQLite ---- - - - -# SQLite - -This section is dedicated to the SQLite database library. On this page, all the steps necessary to start working are described - -
- - -
An external component is used to implement some functions in this library
-Please review the ["About external components"](/docs/Start/Component-requirements) section before getting started
-
- -## About implemented methods - -This library has two parts: basic methods, like connecting and executing SQL queries, and a small ORM for common operations like CREATE, SELECT, INSERT, DELETE, and so on. Working through the ORM and through the query texts executed through the `ExecuteSQLQuery()` function is technically the same: the ORM simply generates the SQL query text based on the layouts, but then also calls them through this function - -By default, all SELECT queries return an array of selected data, while other queries return only `true` in the `result` field on success, or `false` and error text in the `result` and `error` fields, respectively. To execute queries that require data to be returned but are not SELECT queries, the `ExecuteSQLQuery()` function has a `ForceResult` parameter - -## "BLOB" type fields - -This library can process fields of type BLOB (Binary Data). To place a value in a field of this type during INSERT or UPDATE, it can be passed either as a variable of type `BinaryData` (in 1C and OneScript) or as a structure of type `{"blob":File Path}` (in 1C, OneScript and CLI versions). Binary data is always returned as `{"blob":Base64 string}`. - -## Compatibility - +--- +id: SQLite +sidebar_class_name: SQLite +--- + + + +# SQLite + +This section is dedicated to the SQLite database library. On this page, all the steps necessary to start working are described + +
+ + +
An external component is used to implement some functions in this library
+Please review the ["About external components"](/docs/Start/Component-requirements) section before getting started
+
+ +## About implemented methods + +This library has two parts: basic methods, like connecting and executing SQL queries, and a small ORM for common operations like CREATE, SELECT, INSERT, DELETE, and so on. Working through the ORM and through the query texts executed through the `ExecuteSQLQuery()` function is technically the same: the ORM simply generates the SQL query text based on the layouts, but then also calls them through this function + +By default, all SELECT queries return an array of selected data, while other queries return only `true` in the `result` field on success, or `false` and error text in the `result` and `error` fields, respectively. To execute queries that require data to be returned but are not SELECT queries, the `ExecuteSQLQuery()` function has a `ForceResult` parameter + +## "BLOB" type fields + +This library can process fields of type BLOB (Binary Data). To place a value in a field of this type during INSERT or UPDATE, it can be passed either as a variable of type `BinaryData` (in 1C and OneScript) or as a structure of type `{"blob":File Path}` (in 1C, OneScript and CLI versions). Binary data is always returned as `{"blob":Base64 string}`. + +## Compatibility + Technically, the client implementation is a Native component in Rust. It comes in a zip archive format, and, in theory, should work on all available platforms: x86 and x64 Windows and Linux. The actual testing was done on Windows x64 and, cossentially (via OneScript), on Linux x64 \ No newline at end of file