You make a good point here, Juerd. How about i change the do() arguments to this: $dbh->do(tableName => "table_name", get => {...}, set => {...})
Better already, but when in real life is it practical to simultaneously set and get? I can't think of any situation.
Thus abstracting it more, to two methods instead of one, makes sense to me:
Which is very close to what DBIx::Simple lets you write if you have SQL::Abstract installed:$dbh->get("table_name", {...}); $dbh->set("table_name", {...});
$db->select('table_name', [...]); $db->update('table_name', {...}, ...);
Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }
In reply to Re^3: RFC: Simple DBI abstraction
by Juerd
in thread RFC: Simple DBI abstraction
by Jaap
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |