5,576
edits
Changes
Jump to navigation
Jump to search
Esmith::ConfigDB::Record (view source)
Revision as of 16:05, 10 December 2013
, 16:05, 10 December 2013Created page with "=== NAME === esmith::ConfigDB::Record - record in an esmith::ConfigDB database. === SYNOPSIS === Just like esmith::DB::db::Record except... my $value = $record->v..."
=== NAME ===
esmith::ConfigDB::Record - record in an esmith::ConfigDB database.
=== SYNOPSIS ===
Just like esmith::DB::db::Record except...
my $value = $record->value;
$record->set_value($value);
=== DESCRIPTION ===
This provides some extra functionality needed by the esmith::ConfigDB databases.
Unless noted, it works just like esmith::DB::db::Record.
=== New Methods ===
* value
* set_value
my $value = $record->value;
$record->set_value($value);
Gets/sets the value of the $record. Some ConfigDB entries don’t have a set of properties, but rather a single value.
It will warn if you use these on $records with properties.
[[Category:Developer]]
[[Category:SME Server Development Framework]]
[[Category:Development Tools]]
esmith::ConfigDB::Record - record in an esmith::ConfigDB database.
=== SYNOPSIS ===
Just like esmith::DB::db::Record except...
my $value = $record->value;
$record->set_value($value);
=== DESCRIPTION ===
This provides some extra functionality needed by the esmith::ConfigDB databases.
Unless noted, it works just like esmith::DB::db::Record.
=== New Methods ===
* value
* set_value
my $value = $record->value;
$record->set_value($value);
Gets/sets the value of the $record. Some ConfigDB entries don’t have a set of properties, but rather a single value.
It will warn if you use these on $records with properties.
[[Category:Developer]]
[[Category:SME Server Development Framework]]
[[Category:Development Tools]]