this post was submitted on 16 Jul 2023
79 points (98.8% liked)

Programming

17377 readers
257 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] rmam@programming.dev 11 points 1 year ago (1 children)

From the article:

There are a few legitimate downsides to using SQLite. First off, the type system. It's bad. Luckily, as of a month ago, you can use strict typing instead, which somewhat improves the situation.

That's a terribly weak argument. No details, no rationale, not objective evidence, no insightz nothing. "It's bad." That's the full extent of the analysis.

Quite weak.

[โ€“] abhibeckert@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

SQLite's type system could accurately be described as "there is no type system". And the developers consider it a feature not a bug.

A recently added "STRICT" feature changes that. But it's very rudimentary.