Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Commit

Permalink
Update development docs referencing outdated versions of sqlite we no…
Browse files Browse the repository at this point in the history
… longer support (#15498)
  • Loading branch information
H-Shay committed May 2, 2023
1 parent a49b24b commit f3b515f
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 33 deletions.
1 change: 1 addition & 0 deletions changelog.d/15498.doc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Update outdated development docs that mention restrictions in versions of SQLite that we no longer support.
34 changes: 1 addition & 33 deletions docs/development/database_schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -155,43 +155,11 @@ def run_upgrade(
Boolean columns require special treatment, since SQLite treats booleans the
same as integers.

There are three separate aspects to this:

* Any new boolean column must be added to the `BOOLEAN_COLUMNS` list in
Any new boolean column must be added to the `BOOLEAN_COLUMNS` list in
`synapse/_scripts/synapse_port_db.py`. This tells the port script to cast
the integer value from SQLite to a boolean before writing the value to the
postgres database.

* Before SQLite 3.23, `TRUE` and `FALSE` were not recognised as constants by
SQLite, and the `IS [NOT] TRUE`/`IS [NOT] FALSE` operators were not
supported. This makes it necessary to avoid using `TRUE` and `FALSE`
constants in SQL commands.

For example, to insert a `TRUE` value into the database, write:

```python
txn.execute("INSERT INTO tbl(col) VALUES (?)", (True, ))
```

* Default values for new boolean columns present a particular
difficulty. Generally it is best to create separate schema files for
Postgres and SQLite. For example:

```sql
# in 00delta.sql.postgres:
ALTER TABLE tbl ADD COLUMN col BOOLEAN DEFAULT FALSE;
```

```sql
# in 00delta.sql.sqlite:
ALTER TABLE tbl ADD COLUMN col BOOLEAN DEFAULT 0;
```

Note that there is a particularly insidious failure mode here: the Postgres
flavour will be accepted by SQLite 3.22, but will give a column whose
default value is the **string** `"FALSE"` - which, when cast back to a boolean
in Python, evaluates to `True`.


## `event_id` global uniqueness

Expand Down

0 comments on commit f3b515f

Please sign in to comment.