#1424: Work around lack of transactional DDL support
-----------------------------------+----------------------------------------
Reporter: lsmith | Owner: jwage
Type: defect | Status: new
Priority: minor | Milestone:
Component: Migrations | Version: 1.0
Keywords: | Has_test: 0
Mystatus: Pending Core Response | Has_patch: 0
-----------------------------------+----------------------------------------
Unfortunately most RDBMS lack support for transactional DDL (PostgreSQL is
one of the few). So it would be kind of cool if one could run in a super
paranoid mode, that would dump all relevant data before doing any DDL,
that would then automatically get used in the down script.
Alternatively migrations could create new tables, migrate the data and
only when successful drop the old table and rename the new table. This way
no data could be lost or some migration partially applied because of a
screwed up method call in a migration script.
--
Ticket URL: <http://trac.doctrine-project.org/ticket/1424>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"doctrine-svn" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
