Rose::DB::Object::Util(3pm) | User Contributed Perl Documentation | Rose::DB::Object::Util(3pm) |
Rose::DB::Object::Util - Utility functions for use in Rose::DB::Object subclasses and method makers.
package MyDBObject; use Rose::DB::Object::Util qw(:all); use Rose::DB::Object; our @ISA = qw(Rose::DB::Object); ... sub whatever { my($self) = shift; ... if(is_loading($self)) { ... set_state_in_db($self); } ... }
Rose::DB::Object::Util provides functions that are useful for developers who are subclassing Rose::DB::Object or otherwise extending or modifying its behavior.
Rose::DB::Objects have some awareness of their current situation. Certain optimizations rely on this awareness. For example, when loading column values directly from the database, there's no reason to validate the format of the data or immediately "inflate" the values. The is_loading function will tell you when these steps can safely be skipped.
Similarly, it may be useful to set these state characteristics in your code. The "set_sate_*" functions provide that ability.
"Rose::DB::Object::Util" does not export any function names by default.
The 'get_state' tag:
use Rose::DB::Object::Util qw(:get_state);
will cause the following function names to be imported:
is_in_db() is_loading() is_saving()
The 'set_state' tag:
use Rose::DB::Object::Util qw(:set_state);
will cause the following function names to be imported:
set_state_in_db() set_state_loading() set_state_saving()
The 'unset_state' tag:
use Rose::DB::Object::Util qw(:unset_state);
will cause the following function names to be imported:
unset_state_in_db() unset_state_loading() unset_state_saving()
the 'state' tag:
use Rose::DB::Object::Util qw(:unset_state);
will cause the following function names to be imported:
is_in_db() is_loading() is_saving() set_state_in_db() set_state_loading() set_state_saving() unset_state_in_db() unset_state_loading() unset_state_saving()
The 'columns' tag:
use Rose::DB::Object::Util qw(:columns);
will cause the following function names to be imported:
get_column_value_modified() set_column_value_modified() unset_column_value_modified() modified_column_names() has_modified_columns()
The 'children' tag:
use Rose::DB::Object::Util qw(:children);
will cause the following function names to be imported:
has_loaded_related() has_modified_children()
The 'all' tag:
use Rose::DB::Object::Util qw(:all);
will cause the following function names to be imported:
is_in_db() is_loading() is_saving() set_state_in_db() set_state_loading() set_state_saving() unset_state_in_db() unset_state_loading() unset_state_saving() get_column_value_modified() set_column_value_modified() unset_column_value_modified() modified_column_names() has_modified_columns() has_loaded_related() has_modified_children()
If the name is passed as a plain string NAME, then a foreign key with that name is looked up. If no such foreign key exists, then a relationship with that name is looked up. If no such relationship or foreign key exists, a fatal error will occur. Example:
has_loaded_related($object, 'bar');
It's generally not a good idea to add a foreign key and a relationship with the same name, but it is technically possible. To specify the domain of the name, pass the name as the value of a "foreign_key" or "relationship" parameter. You must also pass the object as the value of the "object" parameter. Example:
has_loaded_related(object => $object, foreign_key => 'bar'); has_loaded_related(object => $object, relationship => 'bar');
John C. Siracusa (siracusa@gmail.com)
Copyright (c) 2010 by John C. Siracusa. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
2022-10-14 | perl v5.34.0 |