diff --git a/docs/ff-integrations/database/local-sql/quickstart.md b/docs/ff-integrations/database/local-sql/quickstart.md index 4d7549a3..54a3cb94 100644 --- a/docs/ff-integrations/database/local-sql/quickstart.md +++ b/docs/ff-integrations/database/local-sql/quickstart.md @@ -49,13 +49,18 @@ If you don't yet have an SQLite database, you can easily create one using tools For this example, we'll create a "Notes" table with `ID`, `Title`, `Details`, `DueDate`, and `IsCompleted` as columns. +:::warning +It is advisable to avoid using any SQL reserved keywords such as `type` and `data` as column names to prevent potential build errors or unexpected behavior. SQLite reserves certain words for its SQL syntax, and using these as identifiers without proper handling may cause issues. For a comprehensive list of reserved keywords, refer to the [**SQL reserved words**](https://en.wikipedia.org/wiki/List_of_SQL_reserved_words). +::: + Here's how you can create and configure the database:
- + + :::info[Important to note] SQLite does not have dedicated date-time or boolean data types. For storing date-time values like `DueDate`, we use the integer data type and represent the date-time as a [**UNIX timestamp**](https://www.unixtimestamp.com/). Similarly, for boolean values, such as checking if a note is completed, SQLite uses integers where `0` represents `false` (or not completed) and `1` represents `true` (or completed). :::