Hi, Ok, I've done a lot of what you suggested and put it at: http://elixir.ematia.de/trac/ticket/40
Still using getattr(mapper, '_Mapper__props'), I can't see any other way to get the names of relations. Not done a back-and-forth test, as it doesn't yet run clear back-and- forth - the id columns get set by the database, and it's not possible to pre-set them with the current interface. Not made it py2.3 compatible as yet - downloading it as I type. I guess the other thing that's needed is updates to the documentation. Anyway, I've done a lot of work to tidy this up already, so I hope you can apply it soon. Happy to done some further tidy-ups once we've got an initial version. Paul On Apr 22, 8:39 pm, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote: > On Tue, Apr 22, 2008 at 8:32 PM, Paul Johnston <[EMAIL PROTECTED]> wrote: > > > (probably named "from_dict") and the "to_json" method was renamed to > > > "to_dict" as the output is not really json and I like to have > > > Yes, those are better names. In fact, shall we leave set() as it is, > > so simple sets remain performant? > > Yes, that's what I had in mind. > > > > Seem pretty clean to me. What don't you like about it? > > > The deep parameter seems a bit weird. Anyway, screw it, I'll leave it > > in. > > In fact, me too. But I thought it would be easily fixable by just > renaming it to something else (keys?) and using it without spelling > out the kwarg. > > -- > Gaëtan de Mentenhttp://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 -~----------~----~----~----~------~----~------~--~---
