[Koha-devel] [DISCUSSION] Database schema & coding guidelines

[Kyle Hall]

My favorite solution is to use DBix::Class. With the proper mappings
only keys should really need to be unique. Eventually, the table
classes could in theory hold much of the model code that is in various
C4 modules, in an object-oriented manner.

Kyle

http://www.kylehall.info
ByWater Solutions ( http://bywatersolutions.com )
Meadville Public Library ( http://www.meadvillelibrary.org )
Crawford County Federated Library System ( http://www.ccfls.org )
Mill Run Technology Solutions ( http://millruntech.com )


On Wed, Jun 6, 2012 at 4:22 PM, Paul Poulain <paul.poulain at biblibre.com> wrote:
> Le 06/06/2012 15:55, Kyle Hall a écrit :
>> I agree with paul here. I think in the optimal solution would be a
>> table prefix for every column, so we have *zero* name clashes for
>> joins. I doubt we will get there any time soon, but it is something to
>> thing about. It simplifies queries, whereas having id as the pk for
>> each table convolutes and complicates queries.
>
> Kyle,
>
> I can't remember where I saw this, but it's an old practise, that is not
> recommended anymore (SQL generally speaking)
>
> Plus I think this is something we can't introduce now without rewriting
> a lot of things everywhere.
>
> OTOH, I think updating primary key names is something more achievable,
> even if won't be made in 2 clics, I agree.
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> Tel : (33) 4 91 81 35 08
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at 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/