On 11/8/06, iain duncan <[EMAIL PROTECTED]> wrote: > It's been extremely helpful. Half of me thinks I'm nuts for picking up > Gears a week before the first phase of my project is due, and the other > half is very glad I'm not going to be trying to write a complicated > database-ajaxy app in Django.
You are nuts, though I actually did the same thing. I also use django for content-based sites. The admin is a winner. > On the other hand, I'm still running scared on this whole SO vs SA > thing. I can hack around the primary key issue easy enough because it's > my own DB so I can pop an auto increment id key on the many to many > table and check for repetition myself if I need to. I'm worried that I > am likely to shoot myself in the foot because of doc problems with SA. > Honest opinions on how much of the physical books content is SO > specific? I would assume the docs in the book are much better tested. All official docs for the 1.0 release will push SO as if were the only ORM. I haven't read the book, but I expect that it will have solid coverage of SQLObject and none at all for SA. > How hard is migrating projects from SO to SA anyway? I assume if I use > assign_mapper or turbo entity I can make it such that only the model > code needs to be changed? It depends on how you do your model. You can define a set of intermediate objects and work off these intermediate objects from the rest of your code. I do this on a few projects. For example, in one app I have a TCP object (and UDP, ICMP, they share a base class and table structure) that encapsulates all the functionality the app expects, so it has attributes like TCP.problem_connections and TCP.traffic_history, which mask the queries from the rest of the app. It's read only behavior, though, which makes this easy. Even a full migration where you're querying in the model isn't THAT difficult unless your project is really large, the sql query syntax is fairly similar. It's just the model definition and many to many interactions that really differ between the pojects. I encourage you to make a choice and go with it. If SQLObject gets your project done by next week, then it gets it done. I personally think that if you choose SQLAlchemy, you should read through the tutorial that's been posted on the web and do straight activemapper SA, without the addon libraries. If you do choose SA, you'll have to understand how SA works and roughly how SO works and translate the examples. This is why SA isn't officially recommended for this release. > Thanks again > Iain > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
