On Thu, May 7, 2009 at 12:06 PM, Fabio R. <[email protected]> wrote: > I don't know if you guys like this approach but I think it really make you > focus on your domain and its tests while you are working on it. Since DM > doesn't need the table to build model's properties it means that you don't > need to run migrations every time you make a change to your models. > That's an idea that I got from "Jimmy Nilsson - Applying Domain-Driven > Design and Patterns" book
I think that a few examples would help understanding, and also examples of what DM currently cannot do to help you with your approach, but you would like it to do. Without specific examples I cannot judge any of your points: DM community is in general less opinionated, doesn't mind implementing "features that do not matter" from .NET and Java worlds, but still likes specific examples of how a new feature would make life simpler. usually a conversation about changes in DM hackers IRC channel starts like so: "hey, I was trying to implement adapter/plugin for X and found out that DM currently sucks because of so and so, and here is all the horrible decisions I had to make because of this.... (gist link comes here)" -- MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
