Re: pyDO 2 alpha
Jonathan Ellis <[email protected]> Fri, 22 Apr 2005 14:17:00 -0600
| Newsgroups | gmane.comp.web.skunkweb |
|---|---|
| Message-ID | <[email protected]> |
Jacob Smullyan wrote: > This section of the manual more or less addresses that, although for > it to make sense you have to read the whole document: > > http://skunkweb.org/PyDO2/manual.html#differences-from-pydo-1 Whoops, sorry for not reading all the way to the end there. :) Thanks for the summary. And the new docs do look to be an improvement over the old ones, too. > That's about it. SQLObject is way ahead in terms of community > involvement, and it may be quixotic (oops, wrong framework!) to try to > get anyone interested in PyDO now. But since I'm maintaining it and > using it myself, I thought I should give it the sprucing up it > deserved. I'm actually looking at pyDO because I was immensely unsatisfied with SQLObject. SQLObject wants to own my data, but IMO that's my database's job, not my ORM tool's. (If I wanted it the other way around I'd just use an OODB in the first place.) I don't want to have to declare my constraints to SQLObject when my db enforces them; just let the exception pass through to me if something goes wrong and I'll handle it. This "I own your data, not the db" attitude is bad enough from a Don't Repeat Yourself standpoint, but it's worse, because SQLObject isn't as smart as the db and can't be without re-implementing it entirely. What if I have a unique constraint declared in the database and (okay, this is a crazy example, but what if) I have a trigger that deals with a potential duplicate by moving the old row into an archive table and replacing it with the new one? By throwing an exception at the ORM level, SQLObject breaks things. I was immensely frustrated because I actually do use the power of my database, so having the ORM second-guess me really rubbed the wrong way. (So, uh, are you sure you must feature duplication of db constraints in pyDO2? :) The one thing I did like about SQLObject was the _fromDatabase option. I'm pretty busy with Spyce2 right now, but I might be able to get into pyDO code in a couple weeks. Is the code now or will it be stable enough for eyes other than yours? -Jonathan ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click