Thanks for watching!

I did just that with a small project.  The code hadn't been touched in a 
while, and I had a large number of pending improvements that would 
require schema changes.  I reasoned that the (small) pain of migrating 
to SQLAlchemy would make up for itself with each migration script.

So if this is a fairly feature complete project, you may not make up for 
the initial trouble of migrating. If you have a grand vision to 
implement, then the time saved with Migrate may justify the time spent 
switching.

Some anecdotal numbers:

My small project really was small.  I had two model, plus the identity 
related models.  I spent a few hours doing the conversion, and the 
identity tables gave me the most trouble.  It seems like there was a 
quirk with the table names between the two identity providers that took 
me a while to notice.

If you choose to convert, I'd suggest the following:
* Set aside a couple of hours
* Back up your database
* Use version control like subversion, even if you don't normally.
* Don't forget to change your database URL from "sqlobject.dburi" to 
"sqlalchemy.dburi"

Good luck, and let us know how it goes,

Tim

Ant wrote:
> Interesting screencast. I have a couple of projects which use
> SQLObject (still the default engine), and I've recently had the need
> to modify the schema. Is Migrate a compelling reason to change to
> using SA? And how easy would it be to switch to SA (given that the
> projects are pretty small)? Or does anyone know of a similar tool for
> SQLObject?
> 
> Cheers,
> --
> Ant...
> 
> http://antroy.blogspot.com/
> 
> 
> 
> 
> 
> > 

-- 
Timothy Freund
http://achievewith.us
http://goodcalc.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to