Here is the class for public (read-only) access:

package MyDB;
use base 'Class::DBI';
__PACKAGE__->set_db('Main', 'dbi:mysql:mydb', 'public', 'password');
1;
[download]

Here is the class for staff (read/write) access:

package MyDBUpdate;
use base 'Class::DBI';
__PACKAGE__->set_db('Main', 'dbi:mysql:mydb', 'staff', 'password');
1;
[download]

Here is (part of) a class for one of the six tables:

package Person;
use base 'MyDB';
__PACKAGE__->table('person');
__PACKAGE__->columns(All => qw/
        first_name
        last_name
        street
        city
        state
        zip
/);
1;
[download]

My fear is that, for each of my tables, I need to create a class like this:

package PersonUpdate;
use base 'MyDBUpdate';
__PACKAGE__->table('person');
__PACKAGE__->columns(All => qw/
        first_name
        last_name
        street
        city
        state
        zip
/);
1;
[download]

This would mean duplicating the information for each table, which doesn't seem right. I'm hoping there is something I'm missing. Can someone show me what it is? (Or am I being too paranoid by using a read-only account for public access and a read-write account for staff access?) I did some poking around in Super Search, but didn't find the answer to this. (Or I found it and didn't realize that I had done so!)

While writing this question, I did one last poke around Google and might have found the answer. Perhaps what I need to do is delete MyDBUpdate and instead, for each table, create a class like this:

package PersonUpdate;
use base 'Person';
__PACKAGE__->set_db('Main', 'dbi:mysql:mydb', 'staff', 'password');
1;
[download]

Does that sound right? (Presumably the user ID and password would be pulled from a config file rather than hard-coded in a half-dozen different source files.)