Using rt-setup-database with local version of Handle.pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In order to talk to my RT mysql database via SSL, I had to create a local
customized version of lib/RT/Handle.pm, in which I provide a variable to
BuildDSN (that I set in RT_SiteConfig.pm) specifying a string to be added
to the ‘connect’ statement, pointing to a ‘my.cnf’ file (containing mysql
SSL information). This works fine for normal RT operation.

However, when I try to run rt-setup-database, to update my db schema, it
appears that my local version of Handle.pm is not being used. My db
connect fails because, it appears, $Handle->DSN is returning the value
that the distributed version of Handle.pm would set, rather than what my
local version of Handle.pm should set. So the SSL information not being
supplied to the db connect.

[This schema update worked OK before I started connecting to the db via
SSL and using my customized Handle.pm].

As far as I can tell, rt-setup-database is doing the following:

use lib “/users/ist-rt/RT/rt/ist-rt/local/lib”;
use lib “/users/ist-rt/RT/rt/ist-rt/lib”;

require RT::Handle;

which I would expect to result in my local copy of Handle.pm being used.

Am I missing something here? The fact is, my db connection is failing in
rt-setup-database and this seems to be the result of the Handle->DSN value
that’s being used. The failure is in authenticating to the db, which I
assume is caused by my not supplying the SSL info.

Any suggestions?

Thanks.

Mike

Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://socrates.berkeley.edu/~mikef http://ist.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBRm+FGq0bf1iNr4mCEQLc6gCg6oO0Xe4jLIbbbKSApMezIeiNhKwAnjjw
VH/KmSmxy3RO+ven1dUpeb4M
=Cgpo
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1On Tue, 12 Jun 2007 at 22:48 (-0700), I wrote:

In order to talk to my RT mysql database via SSL, I had to create a
local customized version of lib/RT/Handle.pm, in which I provide a
variable to BuildDSN (that I set in RT_SiteConfig.pm) specifying a
string to be added to the ‘connect’ statement, pointing to a 'my.cnf’
file (containing mysql SSL information). This works fine for normal RT
operation.

However, when I try to run rt-setup-database, to update my db schema, it
appears that my local version of Handle.pm is not being used. … As far
as I can tell, rt-setup-database is doing the following:

use lib “/users/ist-rt/RT/rt/ist-rt/local/lib”;
use lib “/users/ist-rt/RT/rt/ist-rt/lib”;

require RT::Handle;

I found the problem with rt-setup-database. I replaced the above 'use’
statements with this:

use lib qw (/users/ist-rt/RT/rt/ist-rt/local/lib /users/ist-rt/RT/rt/ist-rt/lib);

and then my local version of Handle.pm was picked up.

Anyway, all this is really in relation to a different problem I’m having.
After moving the db from an RT 3.4.5 system to my new 3.6.3 system, and
then running rt-setup-database to apply the db updates that bring 3.4.5 to
3.6.3, I’m still seeing strange symptoms in my web interface:

Inside a ticket display, some of the text from within an attachment is
also appearing on top of the upper part of the screen, sort of overlaying,
or mingling with, the logo and banner of the page. Yet, a 'view source’
of the page doesn’t show that text at the top at all!

Also, the attachment contents themselves are not properly formatted: links
are mixed in with text in an ugly way.

What can be causing this web display weirdness, given that all the data
appears actually to be in the db? (In fact, my dba, who copied over the
3.4.5 db to the 3.6.3 system, says the two versions of the db compared
exactly, byte for byte, before I ran my update scripts).

Thanks.

Mike

Mike Friedman Information Services & Technology
mikef@ack.Berkeley.EDU 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://socrates.berkeley.edu/~mikef http://ist.berkeley.edu

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBRnAjXK0bf1iNr4mCEQLcvwCgixuZOjaRLUzzQNbu38S4YWuf/UIAoLOh
1Adgml2/4BGIH1ijqyRm1Wh5
=3Y00
-----END PGP SIGNATURE-----