search for: zydppglny4us7rsuta25kztv0t984lsv

Hi, Given the convention of fat models to handle business logic, is there a point where you might be justified in using a separate plain ruby object(s) to orchestrate certain business logic interactions, essentially a middle layer between your controllers and models for high level functions? If you look at the InventoryTransaction model below you will see the sort of methods I mean. In this case

Hi, Does anyone know of a tool or script that can parse the contents of the models folder and produce some sort of model relationship document, either a text summary or graphical representation? Thanks, Andrew. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

Hi, I have a model similar Basket shown below. If customer_type is set then it should also set customer to nil. Likewise, if I set customer, it should inspect the customer_type attached to the customer and set accordingly within Basket. However implementing it as below doesn''t seem to work. Am I missing a better way to achieve this? I had also considered using a before_save

Hi, I''m using the new(?) as_json methods within a rest api I am working on. However I am not sure how you are supposed to, or whether it is designed to handle multiple variations of association inclusion. For example I have a model using acts_as_tree, so that each instance has children and a parent: class CatalogueCategory < ActiveRecord::Base acts_as_tree JSON_ATTRS =