Re: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns

Replies are listed 'Best First'.
Re^2: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by Transient (Hermit) on Aug 10, 2005 at 20:41 UTC
This is spot on. The DAO is just an abstraction layer to your actual datasource. The VO's are unnecessary, but then again, it wouldn't necessarily hurt to make a specific one - after all, most objects in Perl are just blessed hashrefs. Throw in some auto-generated getters and setters and you're done.	[reply]
Re^2: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by monsieur_champs (Curate) on Aug 10, 2005 at 22:02 UTC
Shall I use VOs at all? Or this is kind of a purist approach to the problem? Thanks for answering! -- monsieur_champs	[reply]
Re^3: Quite confuse about using Class::DBI to implement Data Access Objects and Value Objects Design Patterns by perrin (Chancellor) on Aug 10, 2005 at 22:23 UTC
In Java, VOs are usually a solution to the problem that remote method calls are very slow and DAOs are often implemented with something that uses remote method calls, like old-school EJBs. I don't think you need them. I don't use them in my perl stuff. It is normal in perl to call methods passing in a hash (the standard "named parameters" pattern). This should be enough.	[reply]