Certainly 3.01.00.009
2140 $dbh->do("ALTER TABLE permissions MODIFY `code` varchar(64)
DEFAULT NULL");
2141 $dbh->do("ALTER TABLE user_permissions MODIFY `code`
varchar(64) DEFAULT NULL");
2016-09-14 21:14 GMT+01:00 Rodrigo Santellan :
> I truncate the tables and
I truncate the tables and try to use the: userpermissions.sql file.
My problem is that code is defined like varchar(30) on update "3.00.00.068"
but on http://schema.koha-community.org/tables/permissions.html is a
varchar(64) I assume the later is the correct. When was this changed?
Regards.
On
module_bit 13 is for tools. From installer/data/mysql/userflags.sql :
INSERT INTO userflags (bit, flag, flagdesc, defaulton) VALUES
(13,'tools','Use all tools (expand for granular tools permissions)',0);
On Wed, Sep 14, 2016 at 1:10 PM, Rodrigo Santellan
wrote:
> I have
I have almost complete the updatadatabase.pl without db errors.
Now I'm missing some data on userflags, what should be the 13 module_bit
Upgrade to 3.00.00.067 done (Updating patronimages syspref to reflect
current kohastructure.sql. )
DBD::mysql::db do failed: Cannot add or update a child row:
Jonathan,
I'm planning to open a bug report and patches when I finish. Don't want
open more than one bug.
I'm adjusting some SQL that are not ok.
Regards
On Wed, Sep 14, 2016 at 4:16 AM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:
> These errors are fixes by 3.01.00.009,
These errors are fixes by 3.01.00.009, certainly because MySQL
strictness has changed since 3.00.00.068
Try to change the 2 code columns to default null.
If it works, please open a new bug report (and attach a patch if you
know how to do it :))
Cheers,
Jonathan
2016-09-13 16:34 GMT+01:00
I think the problem there is that the code column is declared as 'DEFAULT
NULL', where in the permissions table it is declared as 'NOT NULL'. And
the foreign key constraints require an index, as I recall. It seems that
since no primary key is declared it's trying to make one using all the
I found out that on the upgrade 3.00.00.068 the script for creating the
table permissions is wrong:
DBD::mysql::db do failed: All parts of a PRIMARY KEY must be NOT NULL; if
you need NULL in a key, use UNIQUE instead [for Statement "CREATE TABLE
`permissions` (
`module_bit`
Hi,
I have changed: 3.00.00.053 to remove the constraint to labels_templates
and now it goes smooth on that part. I'll add more logging when the db
query are executed because there are some tables like permissions that are
not created.
Thanks a lot!
On Tue, Sep 13, 2016 at 4:29 AM, Jonathan
It has been removed by
commit c102b61ef58dc34860e8acf6cab6bd9a96dae0a1
Date: Mon Jan 4 14:18:01 2010 -0500
[26/30] Updating kohastructure.sql to reflect changes introduced
in Patron Card Creator work
But indeed these changes have not been put in the updatedatabase.pl file.
You can ignore
There's also update 61 which references the labels_templates table. You'd
have to omit that one too.
That table is gone, but I don't know when it gets dropped. I looked
through updatedatabase.pl and didn't see it get dropped. So I don't know.
If you are aiming for a recent release then it
Passing the conditions in true (1 == 1 ) on lines 2623 and 3418 I'm able to
pass further on the updatedatabase.pl
But the problems are on migrating to 3.00.00.053 the definitions that are
needed on that table are on 3.00.00.059. My intuition says to change the
order, but I have to be honest that
Have you looked in the /installer/data/mysql directory at the
labels_upgrade.pl and patroncards_upgrade.pl scripts. I think those where
supposed to be run by the updatedatabase.pl script, but I seem to recall
having trouble with that myself.
On Mon, Sep 12, 2016 at 7:07 AM, Rodrigo Santellan
Hi,
I'm trying to do a migration or upgrade from koha 2.2.3 to koha 3. I know
is a daunting task that I have embarked but I'm trying to bring back a
library to the latest updates of the community.
So far this are the steps I have done:
1 - I dump an empty schema of the DB and create a new one
14 matches
Mail list logo