Possible error in post ‘Auditing and Versioning Data in SQLite’

Open Beginner friendly
#66 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
sql, sqlite
Domain
documentation

Research direction

Open the linked “Auditing and Versioning Data in SQLite” post and locate the suggestion table's valid_to definition. Check the SQLite behavior of NULL versus NOT NULL with the stated default, then update the SQL example if the correction is warranted and verify the rendered post shows the intended definition.

Written by the indexing model from the issue text.

Description

Philipp, thank you for the SQLite versioning post. Just stumbled upon it and it is very helpful indeed.

One small issue: I guess that:

CREATE TABLE IF NOT EXISTS suggestion (
    ...
    valid_to text NULL default '9999-12-31',
    ...
);

should rather read:

CREATE TABLE IF NOT EXISTS suggestion (
    ...
    valid_to text NOT NULL default '9999-12-31',
    ...
);

or am I mistaken?

Dominant language
HTML
Stars
1
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.