Hi Jacques, > Hi. I found another weird edge case that is causing datamapper to blow > up with a binding mismatch error. It seems to be the result of chained > all queries with :conditions specified.
Can you create a ticket for this, and tag it as a "regression"? Raw string conditions are handled completely differently from conditions generated using the hash based API, so there might be issues with them. Even still, I would like to work towards them being as solid as the others, so if you notice any other issues please create tickets for those as well. > Please let me know if the syntax is correct on the gist. Want to make > sure I'm not doing something boneheaded. I should also mention that > this same script runs fine in Datamapper 0.9.11. Yeah, there is a number of refactorings internally inside Query since 0.9.11 that may have broken unspecified behavior for raw queries. What needs to happen is for us to fully specify how raw conditions should be handled, so that if the internal Query code is refactored again (a likely event), there are no regressions in behavior. -- 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 -~----------~----~----~----~------~----~------~--~---
