view release on metacpan or  search on metacpan

MANIFEST  view on Meta::CPAN

Changelog.ini
Changes
data/asset_types.txt
data/event_types.txt
data/menu_orientations.txt
data/os_types.txt
docs/cms.schema.png
docs/html/cms.help.html
docs/pod/cms.help.pod
htdocs/assets/css/app/office/cms/table.tx.css
htdocs/assets/css/app/office/cms/web.page.css
htdocs/assets/templates/app/office/cms/content.js
htdocs/assets/templates/app/office/cms/content.tx
htdocs/assets/templates/app/office/cms/error.tx
htdocs/assets/templates/app/office/cms/page.js
htdocs/assets/templates/app/office/cms/page.templates/generic.page.tx
htdocs/assets/templates/app/office/cms/page.templates/home.page.tx

lib/App/Office/CMS.pm  view on Meta::CPAN

	$self -> log(info  => 'Another message');

=item o Validator.pm

This is used to validate CGI form data.

=back

=item o What's the database schema?

See docs/cms.schema.png.

The file was created with scripts/schema.sh, which uses dbi.schema.pl.

That program is a version of dbigraph.pl, which ships with L<GraphViz::DBI>.

=item o Does the database server have pre-requisites?

The code is DBI-based, of course.

Also, the code assumes the database server supports $dbh -> last_insert_id(undef, undef, $table_name, undef).

scripts/schema.sh  view on Meta::CPAN

DBI_DSN=dbi:Pg:dbname=cms
DBI_USER=cms
DI_PASS=cms
export DBI_DSN
export DBI_USER
export DBI_PASS

dbi.schema.pl svg > docs/cms.schema.svg

echo Wrote docs/cms.schema.png