[MDEV-30359] Alter tables in transactions Created: 2023-01-07 Updated: 2023-01-07 Resolved: 2023-01-07 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Minor |
| Reporter: | Rick Strafy | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Hi, I saw that 11.0 is on the way, so I want to ask, how difficult it would be, to implement DDLs commands to work in transactions. Since it's barely mentioned these days, but that's one of the main reasons people are choosing other DB platforms for serious projects instead of MariaDB, even though MariaDB is faster in most cases. In most modern apps, there are migrations executed in deploy process, if that database migration fails in the middle for some reason (oom killer, wrong sql, different data in production env and so on) and there are some alter tables, database will be broken and there is no simple way to fix it, in platforms like pgsql, whole migration can be packed in transaction, so if something fails, all changes will be reverted and no harm is made. There is a famous quote regarding that: I am marking this as a feature request. source: So I guess it won't be easy, or there is a reason for that? |
| Comments |
| Comment by Sergei Golubchik [ 2023-01-07 ] |
|
it's MDEV-4259, and there's some progress on related tasks and prerequisites. (see Issue Links there), but we didn't start on specifically "transactional DDL" yet. And your guess is right, it won't be easy |