Difference between revisions of "Esmith::ConfigDB::Record"
From SME Server
Jump to navigationJump to search (Created 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) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== NAME === | === NAME === | ||
| − | esmith::ConfigDB::Record - record in an esmith::ConfigDB database. | + | esmith::ConfigDB::Record - record in an esmith::ConfigDB database.<br /> |
| + | |||
| + | In a root terminal you can do the command below if you want to display the up-to-date content | ||
| + | perldoc -U esmith::ConfigDB::Record | ||
=== SYNOPSIS === | === SYNOPSIS === | ||
Latest revision as of 17:44, 20 December 2013
NAME
esmith::ConfigDB::Record - record in an esmith::ConfigDB database.
In a root terminal you can do the command below if you want to display the up-to-date content
perldoc -U esmith::ConfigDB::Record
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.
