On Friday 30 March 2007 20:06:53 Gaetan de Menten wrote: > On 3/26/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > (and whether that be a .query() or Query() or SelectResults not > > > big difference imo.) > > > > i vote Query(). > > I tried to implement it but I couldn't do it the way I wanted to. > The problem is: how do I construct a clause from a clause with bind > parameters + a dictionary containing the values for said bind > parameters? I've only seen bind parameters resolved at execution > time. Is it possible to resolve them earlier? In the attached > patch, I used a workaround which is to store the bind parameters in > the query itself, and then use them whenever the query is executed. i had thought about this before, and i got to 3 stages to put parameters on SA level: - at clause create time - at clause compile time - at clause exec time (actual sql bind_param behaviour) IMO u can keep them parameters there, and allow changes/overriding to occur on each of these stages, and use the result dict at exec time. So what u got is useful IMO.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
