You could always hack around it with Model.find_by_sql - though that returns a frozen struct I think?
Unfortunately I'm not expert enough to reply about other ways to hack around it :) -Kevin On Jul 7, 7:59 pm, David Masover <[email protected]> wrote: > I'm not talking about dm-validations, but, for example: > > class Foo > property :bar, String, :required => true > > ... > > Foo.all :bar => nil > > Currently, this returns 0 records -- DataMapper pre-emptively assumes that > since the conditions aren't valid, no records will match. That's well and good > for 99% of what I do, and I don't want to disturb it: > > http://github.com/datamapper/dm-core/blob/master/lib/dm- > core/repository.rb#L161 > > What I would like is a way around it for the scope of a single query, without > affecting any other queries or other threads -- which is also why I don't want > to just drop the 'required' constraint. > > Is there a clean way to do that? Should there be? -- 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.
