Context Navigation

Changes between Initial Version and Version 1 of Ticket #24535, comment 4

initial	v1
3	3	If you really want to give this a go you can easily override the `migrate` command by wrapping it's `handle` in an `atomic` block for the specified `--database` but you have to keep in mind that'll likely break under certain circumstances and it has the potential to take your side database down if the transaction is held because of a long running operation.
4	4
5		If you really want to roll back on failure you can easily emulate such thing by keeping track of where you are before performing ~~migrating~~ and migrating to the previous state if any exception is raised. This is something you can easily achieve with the commands the migration framework currently exposes.
	5	If you really want to roll back on failure you can easily emulate such thing by keeping track of where you are before performing the migration and migrating to the previous state if any exception is raised. This is something you can easily achieve with the commands the migration framework currently exposes.