This worked fine for us in the end. Did a select on the Content from
the restored old database, and then just updated the Content in the
corresponding row in the new database. We also have similar problems
with other fields, like Headers, where there is any unicode / extended
acsii characters (di
Thanks, it looks like this might work. We basically have a script which
selects the data out of the 3.6 db and then update the corresponding row
in the 3.8 db and so far I'm getting better results.
Thanks,
- Dominic
Aaron Guise wrote:
> Hi,
>
> I too had a similar problem. I inherited our RT Sy
Hi,
I too had a similar problem. I inherited our RT System from an earlier
administrator whom didn't complete some step correctly earlier in the life
of the system. We were going from 3.6.5 to 3.8.0 and all worked fine.
Since then to enable some plugins I attempted to update to 3.8.2.
I did use
> I'm not too clear what you mean. In creating the test system, I did
> backup & restore the db. But I built a 3.6.6 system and then tested the
> upgrade from that database. So I stopped Apache and Postfix, removed
> the old /opt/rt3 folder, make install to get the new 3.8 files, and then
> foll
Hi,
I'm not too clear what you mean. In creating the test system, I did
backup & restore the db. But I built a 3.6.6 system and then tested the
upgrade from that database. So I stopped Apache and Postfix, removed
the old /opt/rt3 folder, make install to get the new 3.8 files, and then
followed
Hmmm, usually the cause of binary attachments not displaying properly is
because folks didn't apply the 'mysql 4.1' update...
James Moseley
Dominic Lepiane wrote:
I did run steps 4-6 from the UPGRADING.mysql , yes. I've included the
generated SQL below. I should note the DBMS is on a sepa
I believe you used backup&restore of original production DB, didn't
you? In this case you probably mangled data on load. Use
--default-character-set=binary on mysqldump and later on mysql load.
This only required for not upgraded DBs, after proper upgrade you
don't need this option.
On Wed, Jun 3,
I did run steps 4-6 from the UPGRADING.mysql , yes. I've included the
generated SQL below. I should note the DBMS is on a separate host from
the RT (Apache / Postfix) server. Actually, now that I think about it,
when I generated the SQL, there was this message:
"Use of uninitialized value in j
Did you apply the schema updates as indicated in steps 4-6 of
UPGRADING.mysql?
James Moseley
Dominic Lepiane wrote:
Dear RT users,
I am trying to get our RT installation moved from RT 3.6.6 to 3.8.3.
I've tried following the upgrade steps in the UPGRADING.mysql and the
README files as dilige
Dear RT users,
I am trying to get our RT installation moved from RT 3.6.6 to 3.8.3.
I've tried following the upgrade steps in the UPGRADING.mysql and the
README files as diligently as I can. The DBMS is MySQL 5.0.45. I
updated all the perl modules... When I try the new version, everything
comin
10 matches
Mail list logo
