new ARGS

ARGS is a hash used to pass parameters to the "_init()" function.

Unless it is overloaded, the _init() function expects one key of 'handle' with a value containing a reference to a Jifty::DBI::Handle object.

id

primary_keys

_accessible COLUMN ATTRIBUTE

DEPRECATED

Returns undef unless "COLUMN" has a true value for "ATTRIBUTE".

Otherwise returns "COLUMN"'s value for that attribute.

_primary_keys

_init_columns

_init_methods_for_columns

schema_version

If no implementation is present, the "latest" schema version is assumed, meaning that any column defining a "till" is not active and all others are.

_init_methods_for_column COLUMN

In addition, if your record class defines the method "schema_version", it will automatically generate methods according to whether the column currently exists for the current application schema version returned by that method. The "schema_version" method must return a value in the same form used by "since" and "till".

If the column doesn't currently exist, it will create the methods, but they will die with an error message stating that the column does not exist for the current version of the application. If it does exist, a normal accessor and mutator will be created.

See also "active" in Jifty::DBI::Column, "since" in Jifty::DBI::Schema, "till" in Jifty::DBI::Schema for more information.

null_reference

Overriding this method to return 0 will cause it to return a record with no id. That is, "<$model-"department>> will return a Department object, but "<$model-"department->id>> will be "undef".

_to_record COLUMN VALUE

It returns "undef" unless "COLUMN" is a valid column for this record that refers to another record class.

If it is valid, this method returns a new record object with an id of "VALUE".

prefetched NAME

add_column

column

    my $column = $self->column($column_name);

Returns the Jifty::DBI::Column object of the specified column name.

columns

    my @columns = $record->columns;

Returns a sorted list of a $record's @columns.

all_columns

  my @all_columns = $record->all_columns;

Returns all the columns for the table, even those that are inactive.

readable_attributes

serialize_metadata

writable_attributes

record values

When you fetch a record value by calling "$my_record->some_field", "Jifty::DBI::Record" provides the following hook

after_column_name

This hook is called with a reference to the value returned by Jifty::DBI. Its return value is discarded.

When you set a value, "Jifty::DBI" provides the following hooks

before_set_column_name PARAMHASH

"Jifty::DBI::Record" passes this function a reference to a paramhash composed of:

before_set PARAMHASH

This is identical to the "before_set_column_name", but is called for every column set.

after_set_column_name PARAMHASH

This hook will be called after a value is successfully set in the database. It will be called with a reference to a paramhash that contains "column", "value", and "old_value" keys. If "value" was a SQL function, it will now contain the actual value that was set. If "column" has filters on it, "value" will be the result of going through an encode and decode cycle.

This hook's return value is ignored.

after_set PARAMHASH

This is identical to the "after_set_column_name", but is called for every column set.

validate_column_name VALUE

This hook is called just before updating the database. It expects the actual new value you're trying to set column_name to. It returns two values. The first is a boolean with truth indicating success. The second is an optional message. Note that validate_column_name may be called outside the context of a set operation to validate a potential value. (The Jifty application framework uses this as part of its AJAX validation system.)

_value

__raw_value

resolve_column

__value

as_hash

_set

load

Takes a single argument, $id. Calls load_by_cols to retrieve the row whose primary key is $id.

load_by_cols

Takes a hash of columns and values. Loads the first record that matches all keys.

The hash's keys are the columns to look at.

The hash's values are either: scalar values to look for OR hash references which contain 'operator', 'value', 'case_sensitive' or 'function'

To load something case sensitively on a case insensitive database, you can do:

  $record->load_by_cols( column => { operator => '=',
                                     value => 'Foo',
                                     case_sensitive => 1 } );

load_by_primary_keys

load_from_hash

_load_from_sql QUERYSTRING @BIND_VALUES

create PARAMHASH

This method creates a new record with the values specified in the PARAMHASH.

This method calls two hooks in your subclass:

before_create

When adding the "before_create" trigger, you can determine whether the trigger may cause an abort or not by passing the "abortable" parameter to the "add_trigger" method. If this is not set, then the return value is ignored regardless.

  sub before_create {
      my $self = shift;
      my $args = shift;

      # Do any checks and changes on $args here.
      $args->{first_name} = ucfirst $args->{first_name};

      return;      # false return vallue will abort the create
      return 1;    # true return value will allow create to continue
  }
    

This method is called before trying to create our row in the database. It's handed a reference to your paramhash. (That means it can modify your parameters on the fly). "before_create" returns a true or false value. If it returns "undef" and the trigger has been added as "abortable", the create is aborted.

after_create

When adding the "after_create" trigger, you can determine whether the trigger may cause an abort or not by passing the "abortable" parameter to the "add_trigger" method. If this is not set, then the return value is ignored regardless.

  sub after_create {
      my $self                    = shift;
      my $insert_return_value_ref = shift;

      return unless $$insert_return_value_ref;    # bail if insert failed
      $self->load($$insert_return_value_ref);     # load ourselves from db

      # Do whatever needs to be done here

      return;   # aborts the create, possibly preventing a load
      return 1; # continue normally
  }
    

This method is called after attempting to insert the record into the database. It gets handed a reference to the return value of the insert. That will either be a true value or a Class::ReturnValue.

Aborting the trigger merely causes "create" to return a false (undefined) value even thought he create may have succeeded. This prevents the loading of the record that would normally be returned.

delete

This method has two hooks:

before_delete

This method is called before the record deletion, if it exists. On failure it returns a Class::ReturnValue with the error. On success it returns 1.

If this method returns an error, it causes the delete to abort and return the return value from this hook.

after_delete

This method is called after deletion, with a reference to the return value from the delete operation.

table

If your class name is "My::App::Rhino", your table name will default to "rhinos". If your class name is "My::App::RhinoOctopus", your default table name will be "rhino_octopuses". Not perfect, but arguably correct.

collection_class

It uses a simple heuristic to determine the collection class name -- It appends "Collection" to its own name. If you want to name your records and collections differently, go right ahead, but don't say we didn't warn you.

_guess_table_name

_handle

PRIVATE refers_to

is_distinct COLUMN_NAME, VALUE

run_canonicalization_for_column column => 'COLUMN', value => 'VALUE'

has_canonicalizer_for_column COLUMN

run_validation_for_column column => 'COLUMN', value => 'VALUE' [extra => \@ARGS]

has_validator_for_column COLUMN

unload_value COLUMN