Can anyone think of any reason to keep the biblioitems.dewey column as a DOUBLE(8,6) type? After installing 2.2.3, I still had problems with this bug, so I did: ALTER TABLE biblioitems MODIFY dewey VARCHAR(10) Everything seems to be working fine -- at least I have yet to find any problems created by this change. Is the dewey column ever part of any numeric functions? If we make this change to the biblioitems table, can we close this bug? -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
Stephen Hedges wrote:
Can anyone think of any reason to keep the biblioitems.dewey column as a DOUBLE(8,6) type? After installing 2.2.3, I still had problems with this bug, so I did: ALTER TABLE biblioitems MODIFY dewey VARCHAR(10) Everything seems to be working fine -- at least I have yet to find any problems created by this change. Is the dewey column ever part of any numeric functions? If we make this change to the biblioitems table, can we close this bug?
Yep, lets do that. Ive made this change to the recent 2.2.x installs ive done, with no ill effects thus far. All I suggest is we make it a varchar(50) or something a bit larger than 10. But making it a varchar of some point is a lot better than have it a double. Chris -- Chris Cormack Katipo Communications Programmer www.katipo.co.nz 027 4500 789
Chris Cormack a écrit :
Stephen Hedges wrote:
Can anyone think of any reason to keep the biblioitems.dewey column as a DOUBLE(8,6) type? After installing 2.2.3, I still had problems with this bug, so I did: ALTER TABLE biblioitems MODIFY dewey VARCHAR(10) Everything seems to be working fine -- at least I have yet to find any problems created by this change. Is the dewey column ever part of any numeric functions? If we make this change to the biblioitems table, can we close this bug?
Yep, lets do that.
Ive made this change to the recent 2.2.x installs ive done, with no ill effects thus far. All I suggest is we make it a varchar(50) or something a bit larger than 10. But making it a varchar of some point is a lot better than have it a double.
Chris
I thought I changed koha.mysql to have dewey being varchar. Seems I was wrong. I changed it in cvs rel_2_2, for 2.2.4. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
I think that we (Ernesto Silva and I) have changed this a lot of month ago. We even comented this issue here, in the developers list. At list in our Koha system this is solved. This solved a lot of problems for us. Andres Stephen Hedges wrote:
Can anyone think of any reason to keep the biblioitems.dewey column as a DOUBLE(8,6) type? After installing 2.2.3, I still had problems with this bug, so I did: ALTER TABLE biblioitems MODIFY dewey VARCHAR(10) Everything seems to be working fine -- at least I have yet to find any problems created by this change. Is the dewey column ever part of any numeric functions? If we make this change to the biblioitems table, can we close this bug?
participants (4)
-
Chris Cormack -
Paul POULAIN -
Stephen Hedges -
Tarallo, Andres