> Actually what you suggest is *not* consistent with the rest of Elixir,
> as other relationship types all imply clearly if they point to one or
> several entities.

That's a fair point, especially in the current HEAD where it's now
been made more clear that the "uselist" keyword argument is not
actually available for use. Personally, I would prefer that there not
be distinct statements for the different cardinalities and that the
use of "uselist" be left to the client. That is, you'd have "has,"
"belongs_to," and "has_and_belongs_to," all nicely orthogonal, and
with "has" and "has_and_belongs_to" taking "uselist," which would be
nicely consistent with SQLAlchemy.

But it's true that that would be a backward-incompatible change, so I
find the introduction of "has_and_belongs_to_one" an acceptable
compromise.

> There is a huge difference between a fork and using a patched version.

Not if the patch isn't accepted back into the mainline, there isn't.

> Besides, I didn't suggest anything particular in that area. There are
> other options... For example, you could add this code in your
> application code, or maybe in a little library on top of elixir if you
> prefer...

It would be silly in the extreme to have "has_and_belongs_to_many" in
the elixir module, but "has_and_belongs_to_one" somewhere else!

Honestly, your reluctance to include "has_and_belongs_to_one" in
Elixir seems to stem entirely from your belief that it is not
semantically different from has_one/belongs_to, which is false, as I
explained in my other reply. I hope, on that basis, that you'll
reconsider.

> --
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to