#887 ✓not-applicable

How about dm-associations ?

Reported by yukiko | June 5th, 2009 @ 06:33 AM

How do you think if I suggest creating a new project like dm-associations
and putting all features like one-to-many, many-to-many etc into that project, as one of dm-more projects?

It may be a way for dm-core to be simple.
It may be a fast fay to be stable.

Supporting associations is one of good and useful features,
but it's easy to cause problems or unexpected behaviors at the same time.

Comments and changes to this ticket

  • Dan Kubb (dkubb)

    Dan Kubb (dkubb) June 16th, 2009 @ 11:05 PM

    • State changed from “unconfirmed” to “not-applicable”

    I'm not sure if DataMapper would be of much use without relationships/associations. I can't see any use for just being able to pull back single Resources without finding any related Resources, or finding children scoped to a specific parents.

    I think for now we'll be keeping associations as part of dm-core, while still keeping the association code as loosely coupled from the rest of dm-core, and just focus on making sure it's rock solid and well tested.

  • yukiko

    yukiko June 18th, 2009 @ 03:16 PM

    Thank you.

    If there is dm-associations,
    I would want to require both dm-core and dm-associations in all my works now.

    But it is the same as dm-aggregates and dm-serializer and dm-timestamps etc..

    They will be used in all cases but I really enjoy the fact they are separated projects.

    I want the reason for separating projects is just keeping each projects simple,

    rather then whether they are definitely needed or not.

    my feeling is that the name "-core" could prevent this project from being simple,

    because it is abstract and have its impression.

    The implementation of associations might depend on the ideas on which each database based.

    Practically, I've never encountered any problems when using datamapper.

    It is about possibility that associations is easy to cause unexpected behavior,

    because it is rather complicated.

    separating projects could help about that.

    And I thought dm-core could be kind of Rack in the ORM world, if it is intended to be.

    But I think I just wanted to suggest. Thank you for your comment.

    I really enjoy watching and using this project.

  • Dan Kubb (dkubb)

    Dan Kubb (dkubb) June 19th, 2009 @ 01:51 PM

    I'm not ruling it out, but I do see associations as a vital part of dm-core.

    I like to try to structure the code so that if I wanted to extract the relationship code from the rest of the project it would be trivial to do so.

    It's true that associations are complex, but I would like to focus on making them work seamlessly across the different adapters first, and it'll probably be easier if we've forced to deal with it because it's part of the core system.

  • yukiko

    yukiko June 19th, 2009 @ 03:57 PM

    I think I understand why you keep asociations in dm-core.

    Thank you very much for explaining.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

People watching this ticket