Paul, > Oh yes, one other thing to consider: We should probably strive to be > backwards compatible. That is, things like: > > Model.all(:name => "Paul", :gender => "dude") > > still work as normal, ANDing the conditions together.
We only really have two constraints with this change: 1) We must provide a simple way to make a query that consists of AND'ed conditions with a Hash (like now) 2) We must not use any methods named the same as in the Enumerable/ Array APIs, but with different usage. Those are "reserved" for future development. In my experience most queries have the conditions are AND'ed together, so we need to keep a simple way to do simple things. What this new syntax really what we're getting is a way to make the hard things possible. Even with this I can still see cases where the complexity of the query reaches a point that it would be simpler to just write SQL or whatever native language your storage engine provides. What we're really doing is raising the bar higher, but I think it will always be there. It's still useful to try to find abstractions that work with multiple adapters so we can continue to raise the bar, but DM will always be constrained by our decision to (try to) not be tightly coupled to RDBMS' way of doing things. -- Dan (dkubb) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
