The stupid question is the question not asked | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Thanks for the annotation. You are surely right - and I know about the caveats of ORMs. Of course one does not need to do it the OO way - but we really need a place to store all the stuff which has to be done whenever records are processed in any way. This can be done in an static module or in an object as well. I think it is attractive to do both (abstraction and collecting all the code) in one step. In regard to stored procedures I do not dare to use them, because we hat massive trouble in using triggers in our replication due to mysql-bugs (which were really tricky to hunt down) and I have no interest in bugtracing mysql's stored procedures with replication... In reply to Re^2: Search for ORM with Multi-Table-Object Support
by Xel
|
|