[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Koha-devel] Database Structure [update strategy : proposal]
From: |
MJ Ray |
Subject: |
Re: [Koha-devel] Database Structure [update strategy : proposal] |
Date: |
Mon, 10 Sep 2007 09:16:31 +0100 |
User-agent: |
Heirloom mailx 12.2 01/07/07 |
MJ Ray <address@hidden> wrote: [...]
> Looking at the 3.0 series changes in updatedatabase, the only thing
> that isn't possible is DropAllForeignKeys - but why is that there?
> We should know what foreign keys we were using and DROP them one by one.
> If we run DropAllForeignKeys on a table, we will also DROP any foreign
> keys installed by a contrib.
>
> paul, hdl and ryan (+ anyone else?) all made the point that one day,
> we may want to make a change that isn't possible with SQL alone. That
> raises a few questions:
>
> - are such fundamental changes a good idea without a version update?
>
> - have we ever made a change which couldn't be done with SQL statements
> and MySQL 5 functions?
>
> - should we use perl-calculated updates every time, or only as a last
> resort?
So are there no changes which couldn't be done with SQL statements and
MySQL 5 functions?
Regards,
--
MJ Ray - see/vidu http://mjr.towers.org.uk/email.html
Experienced webmaster-developers for hire http://www.ttllp.co.uk/
Also: statistician, sysadmin, online shop builder, workers co-op.
Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
- Re: [Koha-devel] Database Structure [update strategy : proposal],
MJ Ray <=