MySQL does not let you have transactional DDL statements (alter, create, index etc).
If you're building anything serious and your data integrity is important, use Postgres.
Postgres is much stricter, and always was. MySQL tried to introduce several strict modes to mitigate the problems that they had, but I would always recommend to use Postgres.
MySQL does not let you have transactional DDL statements (alter, create, index etc).
If you're building anything serious and your data integrity is important, use Postgres.
Postgres is much stricter, and always was. MySQL tried to introduce several strict modes to mitigate the problems that they had, but I would always recommend to use Postgres.
such apps should use sqlite. it's enough for this type of app.
Why mysql instead of postgres should be the right question nowadays.
MySQL or Postgres are the DB of choice if you want a managed database in the cloud.
Probably Postgres is there because you can use it as a queue (https://livebook.manning.com/book/just-use-postgres/chapter-...)
Postgres isn't a newcomer any more. For most projects that I see it's the default and the "classic" already.
Postgres is simply a battle proven technology.
[dead]