Hello, I've worked on two projects now where I've had to use multiparameter assignment on 'virtual' attributes (i.e., non database columns/aggregates). A little Googling led me to other people who have been having the same issue: http://groups.google.ca/group/rubyonrails-talk/browse_thread/thread/59eddeee019a7820/5738b749c978bc40
>From the Lighthouse ticket: "Currently, using multiparameter assignment on a non-column or aggregation throws an error. Since the existing implementation used the reflection to determine whether to create a Date or Time instance to send to the writer, and there's no easy way to infer the desired datatype from the method name or arity, I figured that sending a Time instance for virtual attributes is best in all cases (since a time inherently contains a date.)" Ticket with patch: https://rails.lighthouseapp.com/projects/8994/tickets/2675-support-for-multiparameter-attribute-assignment-on-virtual-attribute-writers Thanks, Brennan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
