[sqlalchemy] Re: [PATCH] Filtered one_to_many relationships (Experimental)
On Mar 31, 2007, at 1:17 PM, Gaetan de Menten wrote: That's approximately what I did in my patch with the new params keyword argument, except I only implemented the set operation, not the add operation on the params. Anyway, what can/should I do to get this included? Do you have any advice/pointers on how to do the same for eager attributes? (or will you implement it yourself?) im totally into a series of engine/execution patches/refactorings right now, so for properties that have lazy=False, there is still a LazyLoader strategy there...you should just call property._get_strategy(LazyLoader) in all cases to get at it. the strategy attribute youre looking at there should really be named _default_strategyand should probably be privately held and accessed via a property (with a docstring, yes), and _get_strategy() should become public (and docstring'ed, yes). the interfaces module youre working with in orm is, trust me, or just go look at the 0.2 source...a work of art compared to how this whole area used to function. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
[sqlalchemy] Re: Firebird backend
Oleg Deribas wrote: Hello, Lele Gaifax said the following on 19.03.2007 17:03: Since I'd be very sad knowing I'm breaking someone else project, I'd like to hear a voice from some other FB user, before asking Michael to accept this work. Here is simple code which works with the stock backend and fails with the new: http://paste.turbogears.org/paste/1138 Sorry for the late answer, but see http://rafb.net/p/dv4lIn88.html and http://rafb.net/p/MkgNud70.html I checked and the role argument is correctly seen by the FB backend, and your script works for me *when* accessing the database as LELE, but effectively not when using SYSDBA, *if* with fails you mean that you get NONE as result. And... I'm ashtonished to ear that it does work for you, with the pristine backend. It may very well be me misunderstanding the roles, as I never used them. Do they work when connecting as SYSDBA? Thank you, bye, lele. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
[sqlalchemy] Re: Automatic generation of changelog
I'd also apreciate if you post your code later. thx in advance. IvO On Mar 28, 6:07 pm, Arnar Birgisson [EMAIL PROTECTED] wrote: Hi Dave, Thank you very much, seems I should be able to do what I want. I'll take a stab at it tomorrow and report. On 3/28/07, Michael Bayer [EMAIL PROTECTED] wrote: note that by history, we mean things that have occured since the instance was loaded from the database into the current session. That history is cleared on session.flush() - right? Arnar --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
[sqlalchemy] Re: Automatic generation of changelog
Gaetan and Ivo: Sure thing. I'll implement this one way or another monday or tuesday, will post what I end up with. Arnar On 4/1/07, imbunche [EMAIL PROTECTED] wrote: I'd also apreciate if you post your code later. thx in advance. IvO On Mar 28, 6:07 pm, Arnar Birgisson [EMAIL PROTECTED] wrote: Hi Dave, Thank you very much, seems I should be able to do what I want. I'll take a stab at it tomorrow and report. On 3/28/07, Michael Bayer [EMAIL PROTECTED] wrote: note that by history, we mean things that have occured since the instance was loaded from the database into the current session. That history is cleared on session.flush() - right? Arnar --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
