Very good, very consitent design. But if people are going to be using this for web apps something like this might be needed

sub oracle_escape {
  
  my $self = shift;
  
  my ($ret_value) = @{{@_}}{qw/dirty/};

  $ret_value =~ s/\'/\'\'/g;
  return $ret_value;
  
}
[download]

and it looks like your presumes autocommit turned on. This is not normally the case, so in that case why not add these

sub commit {
  my $self = shift;
  $self->{'dbh'}->commit();
}
sub rollback {
  my $self = shift;
  $self->{'dbh'}->rollback();
}
[download]

Just some food for thought. Please tell me if you put these in, would be cool to know I helped with something on CPAN ;).

Tradez
"Never underestimate the predicability of stupidity"
- Bullet Tooth Tony, Snatch (2001)

---

In reply to Missing a few methods by tradez
in thread DBIx::Simple by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.