> I think convert from string is not a good solution, because we will
> not be able to use WHERE and ORDER BY queries over attributes (e.g.
> ORDER BY string and number is strongly different).
Yup, that's true. You can of course let Rails do part of the work for
your database, but you don't want to retrieve rows you don't need of
course, so it's probably not the way to go.
> Also I think we need some kind of Query Builder e.g. :orderby => "#
> {attriDef.field}" or :condition=> "#{attriDef.field} = ?".
> "attriDef.field" should return a field name dependent on attribute
> type.
Well, you know what you're looking for, right? If you're comparing an
integer to values in your table, you know you're looking for an
integer. I'm pretty sure Rails can do that for you.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" 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/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
