sqon-parser
Advanced tools
Comparing version 0.1.2 to 0.1.3
{ | ||
"name": "sqon-parser", | ||
"version": "0.1.02", | ||
"version": "0.1.3", | ||
"description": "Structured Query Object Notation. New Database formate (Readable & Supports Binary, Date & Bigint), (Inbuilt Schema & constraints).", | ||
@@ -18,3 +18,3 @@ "main": "./dist/parser.js", | ||
"dist", | ||
"examples" | ||
"example" | ||
], | ||
@@ -21,0 +21,0 @@ "keywords": [ |
@@ -1,3 +0,1 @@ | ||
## Revised SQON Documentation with Strict Mode | ||
### Overview | ||
@@ -19,3 +17,3 @@ | ||
### 1. **Strict Mode (`STRICT=TRUE/FALSE`)** | ||
### 1. **Strict Mode (`*STRICT=TRUE/FALSE`)** | ||
@@ -94,3 +92,3 @@ The strict mode setting, located at the top of the file, controls whether records must strictly adhere to the schema and validation rules. | ||
### Example with `STRICT=TRUE` | ||
### Example with `*STRICT=TRUE` | ||
@@ -122,4 +120,8 @@ ```plaintext | ||
With `STRICT=TRUE`, the format enforces stricter data integrity, providing users with a high degree of reliability and control over data consistency. | ||
With `*STRICT=TRUE`, the format enforces stricter data integrity, providing users with a high degree of reliability and control over data consistency. | ||
### Example usage | ||
For examples, refer to the [test.js](./example/test.js) and [test.sqon](./example/test.sqon) files in the `./example` folder. | ||
### Advantages of SQON Format | ||
@@ -126,0 +128,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Manifest confusion
Supply chain riskThis package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.
Found 1 instance in 1 package
104474
10
1540
132
0