On 7/24/07, Gaetan de Menten <[EMAIL PROTECTED]> wrote: > On 7/23/07, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > > Gaetan de Menten wrote: > > > > Before we release, I'd like to get two things in: > > > > 1. Move to the SQLAlchemy 0.4 convention of a property called > > "query" > > on mapped classes, rather than .query() or .q. > > Agreed. I have a slight preference of .q over .query but I guess > that's something I can live with.
Hmm, this proves more difficult than I thought. We can't have a query property because then assign_mapper fails (it tries to monkeypatch the class and fails). And changing assign_mapper to include a simple has_attr doesn't seem to work either because I'm using a property on the metaclass, not an attribute on the class itself. The only "clean" solution I can think of to actually get a .query attribute is to get rid of assign_mapper entirely (the unclean one being to monkeypatch the class ourselves). -- Gaëtan de Menten http://openhex.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
