Well, I've come across a few. A handful of hanging bugs that I've managed to work around - the latest one to do with dropping/creating tables, different to another one mentioned on here. It's default caching strategy - I recently wrote a performance test to see how my models worked with millions of records, argh - default was they're all stored in memory. It only supports a subset of table management features (correct me if I'm wrong but no way to drop an index etc). Performance madness - that it automatically accesses the database when you set/get fields in the model objects - letting users do users.save() is hardly a mind-strech.
On the other hand code written with it has a simplicity which I really like - more so than the other ORM's I've looked at. In short, it's useful enough (with tweaking) but not quite finished. And before it got finished Ian decided to rewrite it. Yes, I could switch to SQLAlchemy but I'd rather be using TG out of the box especially since there are tool dependencies on SQLObject now. Never mind, guess I'll manage and sit tight for SQLObject2 > > From: Jorge Godoy <[EMAIL PROTECTED]> > Date: 2006/03/16 Thu PM 12:26:36 GMT > To: [email protected] > Subject: [TurboGears] Re: TurboGears ORM status > > > <[EMAIL PROTECTED]> writes: > > > Given that SQLObject is the TurboGears ORM of choice it's surprising that > > there's so little noise on the mailing list. I recently posted there asking > > if there was going to be a 8.0 release but no reply. I get the feeling that > > development on the project has all but dried up. > > I see messages everyday. I can't quantify them, but I'd say it's more than > 10/day. > > > Some of the framework tools now rely on it (CatWalk etc). The author (Ian > > Bicking) has pretty much abandoned the current version in favour of a > > rewrite. > > AFAIK, no indication of a time frame for replacement yet. > > Yet there are other people maintaining SQLObject for a while. So if one of > them is out, it doesn't prevent the other to work wi > > > I know a few other people on here feel a similar way about the situation. > > So, > > I guess what I'm asking is what can we do about our ORM weakness? > > What weaknesses are you talking about? > > -- > Jorge Godoy <[EMAIL PROTECTED]> > > > ----------------------------------------- Email sent from www.ntlworld.com Virus-checked using McAfee(R) Software Visit www.ntlworld.com/security for more information --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
