> I would say: Leave all storage related actions in Koha::Schema. KohaRow does
> not make sense to me.
> Furthermore, define the objects that actually have 'real' business logic and
> put that in some Koha::Object.
Just to add to the confusion ;) When I wrote "some Koha::Object" here, I was
not literally suggesting Koha::Object, I was thinking of something like
Koha::Biblio or Koha::Patron etc.
I would not suggest to add such an object for every table in Koha. We should
clearly define which objects(!) we really need, having sufficient business
logic etc. to justify an interface to DBIx.
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
