Quoting Jonathan Ellis <[EMAIL PROTECTED]>: Sorry you lost me there. I don't see how features requests (which ones?) of me broke sqlalchemy. Basically all I ever was on about was that sqlalchemy works as advertised with oracle.
Now why would I get so incredibly pissed at this caching issue. Well, it's because Michael to my understanding basically told me in one go that I'm a stupid fuckwitt and that I have no business "sneaking" database updates past his mapping code. That ah, did me in for. > The bottom line is, participating in a project doesn't give you the right to > bitch at the lead who is doing far more work than you. (Especially when the > bugs you're complaining about are the direct results of features you > requested yourself!) Neither am I, not at all. > Normally I'm not a fan of the proliferation of solutions to the same > problem, When I not had a deadline to do an actual product which pays my food and shelter in the end, I'd like totally do this. However, since I'm like devoting every waking hour on getting the pleathora of other bugs out and feature requests in it's not really an option for the next few months. And boy I wish that was a lame excuse and I could just take off and do my own ORM and not what my employer thinks is good for his bottom line. I gather people call this prioritizing. I'm sure by the time you'll think I'm crazy. Yeahwell, first there was this meeting 3 months ago. Told my employer that I need 6 man-months to do the thing. Up to now I had opportunity to really work 6 person weeks on it, and next week they'll want a preliminary delivery of a large subset of the thing. Of course I could go like "wtf I told you it's 6 months" but then it'd be back to doing zope or worse java. But look at the bright side, your beloved sqlalchemy will make one of the fastest Alpha software to production, this'll be like four weeks from now, and I've barely begun to do rigorous testing, so whatever you've seen from bug reports from me in the past, fasten your seatbelt it's going up a notch inevitably. > but in this case I think it would be very instructive for you to go > ahead and start your own ORM project like you said you would. Do let us > know how that goes. :) > > On 3/28/06, Florian Boesch <[EMAIL PROTECTED]> wrote: > > > > I originally would've stayed on a stable version, except, it was bugged > > mainly > > for oracle usage, so I *had* to move to the newer versions. > > > > And don't you darn shove the "you lousy slack" up my arse. Do you have > > *any* > > idea how hard it is to isolate a specific mal-behaving combination in a > > huge > > model, extract and rewrite it so I can post it here? > > > > And I didn't do one or two of those! > > > > No Michael has no darn obligation, but the fact is that there is *no* > > other > > usable ORM for oracle in python, and wouldn't there be one, strategically > > my > > whole development would now be java and not python, which for multiple > > reasons > > I don't want, I'm sure you can empathize. > > > > But when you want me to stop thinking of testcases and just simply > > complain that > > things are broken without providing a test-program, just tell me. > > > > -- > Jonathan Ellis > http://spyced.blogspot.com > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
