Re^3: Class::DBI -- does it get any easier?

as i understand it ( and i'm not an expert on it by any means ), there are easy ways to override behaviours if needed, some initialization hooks, etc. if all else were to fail, nothing stops one from going back to 'basic' SQL for some things.

Comment on Re^3: Class::DBI -- does it get any easier?

Replies are listed 'Best First'.
Re^4: Class::DBI -- does it get any easier? by drewbie (Chaplain) on Nov 12, 2004 at 20:09 UTC
I think I didn't properly state my question. Let's say I want to add business logic to the module, say a login() method. This method would take some input and then set/clear columns as appropriate such that a user is now logged in. It might even call methods in other modules. So constraints, triggers, etc would not accomplish this. I assume others are doing the same.	[reply]
Re^5: Class::DBI -- does it get any easier? by geektron (Curate) on Nov 12, 2004 at 21:00 UTC
that's application logic, in my mind, and not data logic ... that's not the goal of Class::DBI. you can do that same get/set operation at the app level, and good MVC would say that you don't do it at the data level.	[reply]