|Just another Perl shrine
Re^3: Maybe database tables aren't such great "objects," after all ...by jordanh (Chaplain)
|on Mar 27, 2011 at 16:46 UTC
I'm not experienced in using ORMs or the architectures being discussed here, but it seems to me that problems might arise if the database structure is too hidden from the people writing and maintaining an application.
How do you maintain transactional integrity in a situation where Perl objects reference multiple tables and different Perl objects might have overlapping table references? It seems to me that sometimes, you want to make sure that a number of Objects being updated result in the database tables being updated atomically and not understanding the impact on the underlying tables might lead one to believe this is being done when it's not. Conversely, you might only want to operate on a single object and have that update the table without waiting on operations on associated objects.
Forgive me if I'm speaking from ignorance of the tools.