I have to say, I have serious problems with SO and heavy-database projects. The main ones are:
1. Maintaining object references, or rather, removing them if an object is destroyed. You can't do Object.destroySelf(), you need to remove all references to it first. This is because SO crashes badly if it comes across a reference to a non-existant object. Which leads me on to: 2. SO pulls too much stuff from the database But also: 3. If SO comes across some bad Unicode data in a database it crashes badly. It provides no method to catch the exception AND find out where the bad data is. I was recently tasked with scanning a 4gb database which I converted to work with SO to find out which of the millions of records had problems. I think SO has an excellent API, but the programming is too unmaintainable and incomplete to make me want to try doing anything with it in the future. Bring on the SA compat layer! -Rob Max Ischenko wrote: > For a short-term project (say, a couple of months) SQLObject is > probably a better choice - easier to get started, most things you may > need will work. > > For a longer term project I'd seriously consider SQLAlchemy - quality > of developemnt & docs yields more benefits than SO' familiarity. > > Just my opinion, > Max. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
