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

[perrin]

There is no need to use Value Objects in Perl. These can just be hashes. Class::DBI classes are your DAOs.

[Transient]

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.

[monsieur_champs]

Shall I use VOs at all? Or this is kind of a purist approach to the problem?

Thanks for answering!

[perrin]

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.