News for hackers. Stuff that matters.
Re:Why favor PostgreSQL over MariaDB/MySQL? by developer2 on Tuesday September 05, 2017 @03:23AM (#15173138)
This is one of the many reasons I prefer postgres, but it's worth noting that even in postgres, there are some DDL statements that cannot be executed within a transaction. I can't remember the list, but they do exist - it's just a far smaller number compared to MySQL.
Re:Why favor PostgreSQL over MariaDB/MySQL? by adrianmsmith on Tuesday September 05, 2017 @03:50AM (#15173271)
For example adding a value to an enum type: https://www.postgresql.org/docs/9.6/static/sql-altertype.htm...

(This bit me recently, because our database migration framework (correctly) puts transactions around migrations, and PostgreSQL (correctly) fails with an error in the case you try to do an operation in a transaction which can't be done in a transaction. (I say correctly, as opposed to Oracle/MySQL which will silently do commits etc.))

Re:Why favor PostgreSQL over MariaDB/MySQL? by pritambaral on Tuesday September 05, 2017 @12:40PM (#15176832)
I have been in this situation. I then wondered if it was indeed right for my database migration tool to forcibly wrap migrations in transactions and not let me override that behaviour.
Re:Why favor PostgreSQL over MariaDB/MySQL? by emeijer on Tuesday September 05, 2017 @09:28AM (#15174845)
Actually, as of the next version (10) you can :)