- SEE ALSO
Jifty::Action::Record -- An action tied to a record in the database.
To actually use this class, you probably want to inherit from one of Jifty::Action::Record::Create, Jifty::Action::Record::Update, or Jifty::Action::Record::Delete. You may need to override the "record_class" method, if Jifty cannot determine the record class of this action.
Access to the underlying Jifty::Record object for this action is through the
This method can either be overridden to return a string specifying the name of the record class, or the name of the class can be passed to the constructor.
If the action returns true for
report_detailed_message, put the per-field messages as
detailed_messages in the result content for Update actions. The default is true.
Construct a new
Jifty::Action::Record (as mentioned in Jifty::Action, this should only be called by
record value, if provided in the PARAMHASH, will be used to load the "record"; otherwise, the primary keys will be loaded from the action's argument values, and the "record" loaded from those primary keys.
This also creates built-in validation and autocompletion methods (validate_$fieldname and autocomplete_$fieldname) for action fields that are defined "validate" or "autocomplete". These methods can be overridden in any Action which inherits from this class.
Additionally, if our model class defines canonicalize_, validate_, or autocomplete_ FIELD, generate appropriate an appropriate canonicalizer, validator, or autocompleter that will call that method with the value to be validated, canonicalized, or autocompleted.
validate_FIELD should return a (success boolean, message) list.
autocomplete_FIELD should return a the same kind of list as Jifty::Action::_autocomplete_argument
canonicalized_FIELD should return the canonicalized value.
Returns the list of columns objects on the object that the action can update. This defaults to all of the
containers or the non-
virtual and non-
serial columns of the object.
Returns the list of the "possible_columns"' names.
Usually at the end names are required, however for subclassing column objects are better, or this method in a subclass turns out to be "map to column" - "filter" - "map to name" chain.
Throws an error unless it is overridden; use Jifty::Action::Record::Create, ::Update, or ::Delete
Jifty is Copyright 2005-2010 Best Practical Solutions, LLC. Jifty is distributed under the same terms as Perl itself.