Hi All,
  I'm about to split up my database module into 3 or 4 smaller more specific modules. At the moment I'll calling all the routines as methods, such as:-

package database_mod;
use DBI;

our $dbh;

sub connect {
    $dbh->### DBI connect
}#sub

sub add_user {
    $dbh->### DBI SQL, ETC
}#sub

sub report {
    $dbh->### ETC
}#sub
[download]

Using it with:-

use database_mod;

database_mod::connect();

database_mod::add_user();

### etc
[download]

Now I'm thinking if I split it up and keep using this method things will get messy.

package database_mod;
use DBI;

our $dbh;

sub connect {
    $dbh->### DBI connect
}#sub

package database_user;
sub add_user {
    $database_mod::dbh->### DBI SQL, ETC
}#sub

package database_report;
sub report {
    $database_mod::dbh->### ETC
}#sub
[download]

Using it with:-

use database_mod;
use database_user;

database_mod::connect();

database_user::add_user();

### etc
[download]

So I'm wondering if now is a good time to switch the database system to OO Perl? I've not really written much at all in the way of OO Perl. But I'm guessing it'd be something like:-

package database_mod;
use DBI;

sub new {
    ### $class, $self, bless n all.
}#sub

sub connect {
    $self->### DBI connect
}#sub


package database_user;

use base database_mod;

sub add_user {
    $self->### DBI SQL, ETC
}#sub


package database_report;

use base database_mod;

sub report {
    $database_mod::dbh->### ETC
}#sub
[download]

Using it with:-

use database_mod;
use database_user;

my $db = new database_mod;
$db->connect();

$db->add_user();

$db->report();

### etc
[download]

Would this be the best way to go? Certainly looks a lot cleaner, but would it be OO for the sake of OO? Have I got the OO package logic right? Or should I stick to using methods like before?
I'm sure many of you have a lot more OO Perl experience than me.


Lyle