On 11 Jul 2010, at 14:48, Leandro Hermida wrote
<snip>
In many software development projects particularly business-related you really the database to be a relational implementation of your entity object model because you have other systems, software and programming languages that will be interacting with the database.
<snip>
Actually the poster is misleading. When you change the database layout you don't have to change the apps which work on that data model interface - because you already have an abstracting layer between the application and the database. You can extend your ORM implementation to be backwards compatible, so that the actual data store behind it can change but the front face does not.
That entirely doesn't work in the situation described by the post which I was replying to..
Extending your ORM implementation doesn't do anything to help you if you're accessing the same database from other programming languages (ergo through an entirely different data access layer).
Cheers t0m _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
