(bump) On Tue, Jan 20, 2009 at 5:00 PM, Greg Hauptmann < [email protected]> wrote:
> Hi, > > I have an "automation" model with some config data. When it runs it looks > across other models and does some matching, however it also builds up a list > of "duplicate data" type issues identified as part of the routine. > > In terms of how I capture this array of duplicate data issues and pass to a > view for display what would Rails best practice suggest? For example: > * use validation framework (e.g. add_to_base, and then the helper tags to > display) even though the data is not associated with attributes in the model > * extend an application_error Exception to include an Array > * just use an array to pass back to controller, which stores as an instance > variable (@duplicates) and write custom code to display in view (i.e. won't > use error/validation tags) > > thanks > > > -- > Greg > http://blog.gregnet.org/ > > > -- Greg http://blog.gregnet.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
