<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19403"></HEAD>
<BODY><!-- Converted from text/plain format -->
<P><FONT size=2>> On Wednesday, 10 Apr 2012, Ruslan wrote:<BR>> > Thank
you for the pointer to github.<BR>> ><BR>> > I looked. Based on what
tables and columns are present, I conclude<BR>> > that the database
updates for 3.3.0 and 3.3.11 were run, but for<BR>> > reasons unknown, the
very last part of the 3.3.0 database update,<BR>> > beginning with 'ALTER
TABLE CustomFields ...' and including 'UPDATE CustomFields...'<BR>> > did
not occur. On the other hand, dropping the Current column from<BR>> > the
TicketCustomFieldValues table in the 3.3.11 update did occur.<BR>>
><BR>> ><BR>> The only idea is that intermediate step failed and
this was not noticed by administrator, so he just continued further.<BR>>
><BR>> ><BR>> > My best idea is to apply the missed portion of
the updates and<BR>> > proceed, along the lines of the shell script below.
Not ideal, but<BR>> > I don't know a better approach that does not involve
time travel.<BR>> > That approach generates one warning during the
generation of the queries.sql file:<BR>> ><BR>> > Use of
uninitialized value in join or string at<BR>> >
/usr/share/request-tracker3.8/etc/upgrade/upgrade-mysql-schema.pl line
261.<BR>> > .Groups.Instance has type VARCHAR however mapping is
missing.<BR>> ><BR>> ><BR>> In upgrade scripts find ALTER TABLE
that changes Instance from VARCHAR to INTEGER.<BR><BR>Ruslan,<BR><BR>Thank you
for this helpful suggestion. In the rt-3-0-8/UPGRADING file, found at <A
href="http://download.bestpractical.com/pub/rt/release/rt-3-0-8.tar.gz">http://download.bestpractical.com/pub/rt/release/rt-3-0-8.tar.gz</A>,
I found these recommended changes for
Postgres:<BR><BR>Postgres<BR>--------<BR>If you have a Postgres database, the
following changes to your database can improve performance:<BR><BR>ALTER TABLE
groups rename instance to instance1;<BR>ALTER TABLE groups add instance
int;<BR>UPDATE groups SET instance = instance1::text::int where btrim(instance1)
<> '';<BR>ALTER TABLE groups drop column instance1;<BR><BR>Modifying these
for MySQL as shown below, and executing these changes prior to the partial
updates for 3.3.0 removed the warning during the generation of the queries.sql
file.<BR><BR>ALTER TABLE Groups CHANGE Instance Instance1 varchar(64);<BR>ALTER
TABLE Groups ADD COLUMN Instance integer;<BR>UPDATE Groups SET instance =
convert(Instance1, unsigned) WHERE trim(Instance1) <> '';<BR>ALTER TABLE
Groups DROP COLUMN Instance1;<BR><BR>Thanks,<BR><BR>Ken<BR><BR>> ><BR>>
> All of the other operations have no complaints.<BR>> ><BR>> >
Ken<BR>> ><BR>> ><BR>> Best regards,
Ruslan.<BR><BR></FONT></P></BODY></HTML>