#2221: wrap db upgrade scripts in a transaction
------------------------+----------------------
Reporter: dustin | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: 0.8.6
Version: 0.8.5 | Resolution: wontfix
Keywords: database |
------------------------+----------------------
Changes (by dustin):
* status: new => closed
* resolution: => wontfix
Comment:
Now I remember why I didn't do this before!
Upgrade scripts take engines, not connections. Connections are the tie-in
for transactions, so there's not a comfortable way to wrap each upgrade
step in a transaction.
More to the point, sqlite doesn't support schema modifications as part of
transactions, and MySQL just doesn't (really) support transactions, so
this would only work for Postgres, anyway.
--
Ticket URL: <http://trac.buildbot.net/ticket/2221#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
