Interesting. OpenStruct might very well come in handy. Thanks. On Oct 7, 8:42 am, Michael Pavling <[email protected]> wrote: > On 7 October 2010 13:15, jrq <[email protected]> wrote: > > > On Oct 7, 4:50 am, Michael Pavling <[email protected]> wrote: > >> I've read the rest of the thread with interest, but I just wanted to > >> go back to the start for a second. > > > <snipped lots more good info> > > Okay, well, given you want to try to make your life easier in a very > special and specific use-case, and I can see a bit more about the > angle you're coming at this problem; If you're going to > programmatically solve this in a potentially quick-and-dirty way, > because the powers-that-be must be demanding the "reports", try seeing > if OpenStructs [1] will help you build up collections of > pseudo--relational-records made up from the EAV records. They're a > nice solution for creating "something" that behaves like an AR object > for the majority of time - you could even extend one of the "tableless > model" [2] implementations to keep more standards in your interfaces. > > [1]http://ruby-doc.org/stdlib/libdoc/ostruct/rdoc/classes/OpenStruct.html > > [2]http://stackoverflow.com/questions/937429/activerecordbase-without-ta... > or Google for others...
-- 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.
