> That change was not meant to discourage using uselist. It was meant to > make it possible to inherit from has_and_belongs_to_many and override > uselist.
Quite right, which is what I now do in my patch. Thanks! > Well, I finally understood what you meant. There is indeed a different > semantic to it. Sorry for not getting it earlier... No worries--the issues in ORM, as you know better than I, can be subtle. :-) > Besides, I forgot > to tell you I made a change a few days ago which should allow you to > do _almost_ what you'd like: now keywords passed to the relationship > override those computed (or precoded) by Elixir. It means you should > be able to declare your relationship as: > > has_and_belongs_to_many(..., uselist=False) That does indeed support my old usage pattern, but I find your argument that "...many(... uselist=false)" is inconsistent with the other statements in Elixir persuasive. > As for the has_and_belongs_to_one, if you provide a patch (with > documentation similar to the other relationship types), I'll include > it. Great, thanks! I'll upload my patch to the "Files" section of the group immediately. It includes the implementation, docs, and a test. Thanks for all your help! > -- > Gaëtan de Mentenhttp://openhex.org Best regards, Paul Snively --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
