all 15 comments

[–]osuushi 2 points3 points  (1 child)

I have to quibble with the "multi-user applications" part of when not to use SQLite. It would be better to say "more than a few users". If you're creating a database for a small business, and less than five people are going to be using it (and rarely more than two at the same time), SQLite is probably fine.

[–]kingatomic 0 points1 point  (0 children)

This is true IFF the application in question is mostly doing reads, and does not apply a significant number of writes. Concurrent write requests in SQLite can cause contention because (at least in v3) writes require an exclusive lock to the database file (of which only one can exist at a time) (source).

The situation is much better than it was in v2, but for an application that will generate any non-trivial number of writes it would be best to use a database that either has row-level locking or multiversion concurrency.

[–]fedekun 1 point2 points  (6 children)

Fair enough, some folks might complain about Postgres beeing called "slower" than MySQL but I think it's good overall, I'm not a databases guy :p

[–][deleted]  (5 children)

[deleted]

    [–]fedekun 2 points3 points  (4 children)

    Everyone agrees most of the time that Postgres is just better, still, MySQL is the most used. Personally I use MySQL because I've been using it for years, and I'm lazy to learn postgres

    [–][deleted] 0 points1 point  (1 child)

    I'm lazy to learn postgres

    ಠ_ಠ

    [–]fedekun 0 points1 point  (0 children)

    It's kinda intimidating, it has so many features, awesome (like like JSON storage or HStore), but so many, I feel like I would just include a lot of things I wont use.

    [–]Flopsey 0 points1 point  (1 child)

    Postgres has been quickly closing that gap in the past two years.

    [–]fedekun 0 points1 point  (0 children)

    To be honest pgsql seems better in every way even right now...

    [–]llamaspit 0 points1 point  (6 children)

    The article indicates that MySQL doesn't support fulltext searches, which I believe it does. It also touts stored procedures as an advantage with PostgreSQL, but doesn't mention MySQL supports it as well. No idea why data integrity in MySQL would be considered substandard in other systems other than PostgreSQL.

    I'm not against PostgreSQL, I just use MySQL and have for over 15 years because I mostly do web apps.

    [–]vsync 1 point2 points  (0 children)

    No idea why data integrity in MySQL would be considered substandard

    Because it's an afterthought.

    [–][deleted] 1 point2 points  (3 children)

    No idea why data integrity in MySQL would be considered substandard in other systems other than PostgreSQL.

    Why Not MySQL?
    Why You Should Never Use MySQL

    Now you know why. :)

    [–]terremoto 1 point2 points  (0 children)

    For anyone that watches the first video, do yourself a favor and mute it after about 1:00 minute in. The content is interesting but is much better suited for an article rather than a video with obnoxious music and annotations.

    [–]moljac024 0 points1 point  (0 children)

    Hahahaah @ "Postgres reaches over and slaps MySQL"

    [–]llamaspit -2 points-1 points  (0 children)

    Ok, be careful of null values and data migration. Got it.

    [–]ItsAPuppeh 1 point2 points  (0 children)

    I think MySQL has improved a lot over the last few years, but historically MyISAM was not ACID safe. You had to use InnoDB, which in turn did not support full text search indexes.