DBIx::Class, in all likelihood, will be the real solution. As the author of
C4::Table, I still think it is cool, easy to use and relatively tight, but
it's unfinished, and there won't be a real need for it once we have
DBIx::Class involved.
--Joe
On Thu, Nov 13, 2008 at 4:59 AM, Rick Welykochy <
Joe Atzberger wrote:
> The purpose of Table is to provide all the basic functionality that
> is reimplemented multiple times throughout Koha for each DB table.
> This code is considered experimental and does not yet supplant any
> production code. Please examine and test, like:
> use C4::Tabl
On Wed, Nov 5, 2008 at 5:42 AM, Paul POULAIN <[EMAIL PROTECTED]> wrote:
> Joe Atzberger a écrit :
> > Paul --
> >
> > I think you mean all the SQL should be in C4, and yes I agree with
> > that. C4::Table does not receive any SQL as arguments to select, insert
> > or delete. I.E., it preserves t
Joe Atzberger a écrit :
> Paul --
>
> I think you mean all the SQL should be in C4, and yes I agree with
> that. C4::Table does not receive any SQL as arguments to select, insert
> or delete. I.E., it preserves the encapsulation of SQL inside C4/*.
>
> This would speed up development of featu
Paul --
I think you mean all the SQL should be in C4, and yes I agree with that.
C4::Table does not receive any SQL as arguments to select, insert or
delete. I.E., it preserves the encapsulation of SQL inside C4/*.
This would speed up development of features because a C4/NewFeature.pm
module mig
Joe Atzberger a écrit :
> The purpose of Table is to provide all the basic functionality that
> is reimplemented multiple times throughout Koha for each DB table.
> This code is considered experimental and does not yet supplant any
> production code. Please examine and test, like:
> use C4::Ta
