2.x > 3.x

-----BEGIN PGP SIGNED MESSAGE-----

Wondering if this is possible. If I take an sql dump from an old rt
server (it might be rt-2-0-13) and load it into my own db, can the rt dumper
grab it from there without installing rt2? The perl version is so old on the
rt 2.x server I can’t even run the rt-2.0-to-dumpfile script.


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPmz1v1PEkLgodAWVAQFoLQP+Kujt6pd1gRdo5JuLYCfO0BdsqzxmcZDJ
Qer0lvE2o425nGyJpdCYyxhDW8xXVb45vGzPQGqmQxsrBvbA985VnZAYt6MgY/oz
zLfp8AJ52/BoIUDuKXih69QZcxK5AA4uqrR0weCKi1uOjCg8w47OKeDZ5vV9vuLP
W8n19cDOGE8=
=cIA1
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----

Wondering if this is possible. If I take an sql dump from an old rt
server (it might be rt-2-0-13) and load it into my own db, can the rt dumper
grab it from there without installing rt2? The perl version is so old on the
rt 2.x server I can’t even run the rt-2.0-to-dumpfile script.


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPm3lulPEkLgodAWVAQEEwwP8CKw/Z2ILsCz2KOYBejHupM7CfgvZFcsc
GDMt1KOUGQjlq+X4tzAZlE0+z7vtvHgRNqMDkX5Q5h+Kc9jVHGHzaemBjNpNKul3
903c/hsVeUeOoF2P/fXdX+0F3k8wAnMDzVZwATQQU3LpwL7o+5NkLlqMm9CfPjUE
KOSfz0+2hyo=
=lk88
-----END PGP SIGNATURE-----

Wondering if this is possible. If I take an sql dump from an old rt
server (it might be rt-2-0-13) and load it into my own db, can the rt dumper
grab it from there without installing rt2?

You’ll still need the RT2 libraries, which the dumper uses. These can be
copied from the old server into a temporary directory, and appropriate
’use lib’ (rt2-dumper) and $DatabaseHost changes (config.pm) will work.

( ie, theres varying levels of ‘install’ :wink: )

The perl version is so old on the
rt 2.x server I can’t even run the rt-2.0-to-dumpfile script.

Which version of perl is ‘so old’ ?

                         Bruce Campbell                            RIPE
               Systems/Network Engineer                             NCC
             www.ripe.net - PGP562C8B1B             Operations/Security

-----BEGIN PGP SIGNED MESSAGE-----

You’ll still need the RT2 libraries, which the dumper uses. These can be
copied from the old server into a temporary directory, and appropriate
’use lib’ (rt2-dumper) and $DatabaseHost changes (config.pm) will work.

( ie, theres varying levels of ‘install’ :wink: )

Ok, did this and it loaded up the dump directory with t-* files and metadata.
Now, trying to go the other way, I get this.

./dumpfile-to-rt-3.0 rt2dump

[Tue Mar 11 15:16:37 2003] [err]: Couldn’t load from the users database.
(/opt/rt3/lib/RT/CurrentUser.pm:112)
WARNING: pg_atoi: zero-length string
WARNING: pg_atoi: zero-length string
Creating 27 - GWI-CSS
WARNING: pg_atoi: zero-length string
WARNING: pg_atoi: zero-length string
[Tue Mar 11 15:16:37 2003] [crit]: Failed to create user for$VAR1 =
‘HASH(0x8cc7a04)
No permission to create users
’;
(/opt/rt3/lib/RT.pm:230)

Since it’s whining about creating users, I ended up going through my postgres
server and giving every single user full access as well as full privs on the
table itself, but still get the above message. I even rigged it up to su to
the user that my postgres server is running and get the same results. Any
clues?

Which version of perl is ‘so old’ ?

% perl -v

This is perl, version 5.005_03 built for i386-bsdos

I was getting a very similar error to one that I was getting before I fixed my
perl install on my own machine.


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPm4EXlPEkLgodAWVAQGCWwQAihcVkeMFaTuOujp7DX2Irjnxbzc1aVKB
iSOxy8VJ/o+D7l+ZbUz3+s6FW+748ea8WwUStXylMwzgb5/EAji0ebvwlWZDYB/Z
TO55nWkHOtyqV+46/zz6RvF2W1KWLQSiodVEJlMnglgCmrsg3CWZL+JKEbkgXhMb
pQPIT9QmaV8=
=Goz8
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----

./dumpfile-to-rt-3.0 rt2dump

[Tue Mar 11 15:16:37 2003] [err]: Couldn’t load from the users database.
(/opt/rt3/lib/RT/CurrentUser.pm:112)
WARNING: pg_atoi: zero-length string
WARNING: pg_atoi: zero-length string
Creating 27 - GWI-CSS
WARNING: pg_atoi: zero-length string
WARNING: pg_atoi: zero-length string
[Tue Mar 11 15:16:37 2003] [crit]: Failed to create user for$VAR1 =
‘HASH(0x8cc7a04)
No permission to create users
’;
(/opt/rt3/lib/RT.pm:230)

I managed to isolate the problem to some specific lines in the
dumpfile-to-rt-3.0 script.

these lines:

print "–step 10–params " . %{params} . “–\n”;
$so->Create(%params);
print “–step 11\n”;

generate this output:

  • –step 10–params 3/8–
    [Tue Mar 11 18:53:30 2003] [err]: Couldn’t load from the users database.
    (/opt/rt3/lib/RT/CurrentUser.pm:112)
    WARNING: pg_atoi: zero-length string
  • –step 11

and these lines:

print “\nstep 16\n”;
print "Creating $old_id - " . $user->{‘Name’} . “\n”;
print “\nstep 17”;

generate this output:

step 16
Creating 27 - GWI-CSS

WARNING: pg_atoi: zero-length string
[Tue Mar 11 18:58:56 2003] [crit]: Failed to create user for$VAR1 =
‘HASH(0x8ce6e4c)
No permission to create users
’;
(/opt/rt3/lib/RT.pm:231)
step 17


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPm4yZlPEkLgodAWVAQG/HAQAo9gfRsS/9nqAiUvkDlBfXLyH4JoCUUWr
proA4m+m8vAbOeCXowBRa4Q4oer6ZbwRlLBEiw4o0xUzpcsoZxqAQlQAZGndKbm5
gCyZ0JQzp69v3PzwundlKiI11wJqLXdK+LAWQyB3BXW5Xl0wOZtHtqWCyA8B1UTH
hbhAG0ruUhk=
=CTqR
-----END PGP SIGNATURE-----

you’re trying to use RT 2.0 on Postgres 7.3. That’s not going to work.On Tue, Mar 11, 2003 at 02:00:55PM -0500, Andy Harrison wrote:

-----BEGIN PGP SIGNED MESSAGE-----

./dumpfile-to-rt-3.0 rt2dump

[Tue Mar 11 15:16:37 2003] [err]: Couldn’t load from the users database.
(/opt/rt3/lib/RT/CurrentUser.pm:112)
WARNING: pg_atoi: zero-length string
WARNING: pg_atoi: zero-length string
Creating 27 - GWI-CSS
WARNING: pg_atoi: zero-length string
WARNING: pg_atoi: zero-length string
[Tue Mar 11 15:16:37 2003] [crit]: Failed to create user for$VAR1 =
‘HASH(0x8cc7a04)
No permission to create users
’;
(/opt/rt3/lib/RT.pm:230)

I managed to isolate the problem to some specific lines in the
dumpfile-to-rt-3.0 script.

these lines:

print "–step 10–params " . %{params} . “–\n”;
$so->Create(%params);
print “–step 11\n”;

generate this output:

  • –step 10–params 3/8–
    [Tue Mar 11 18:53:30 2003] [err]: Couldn’t load from the users database.
    (/opt/rt3/lib/RT/CurrentUser.pm:112)
    WARNING: pg_atoi: zero-length string
  • –step 11

and these lines:

print “\nstep 16\n”;
print "Creating $old_id - " . $user->{‘Name’} . “\n”;
print “\nstep 17”;

generate this output:

step 16
Creating 27 - GWI-CSS

WARNING: pg_atoi: zero-length string
[Tue Mar 11 18:58:56 2003] [crit]: Failed to create user for$VAR1 =
‘HASH(0x8ce6e4c)
No permission to create users
’;
(/opt/rt3/lib/RT.pm:231)
step 17


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPm4yZlPEkLgodAWVAQG/HAQAo9gfRsS/9nqAiUvkDlBfXLyH4JoCUUWr
proA4m+m8vAbOeCXowBRa4Q4oer6ZbwRlLBEiw4o0xUzpcsoZxqAQlQAZGndKbm5
gCyZ0JQzp69v3PzwundlKiI11wJqLXdK+LAWQyB3BXW5Xl0wOZtHtqWCyA8B1UTH
hbhAG0ruUhk=
=CTqR
-----END PGP SIGNATURE-----


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

you’re trying to use RT 2.0 on Postgres 7.3. That’s not going to work.

Hmmm. That’s an aspect I hadn’t thought of: how much trouble am I in
when I try to upgrade to RT 3, since I’m runing 2.0 on PG 7.3?

-Robin

http://www.digitalkingdom.org/~rlpowell/ *** I’m a male Robin.
.i le pamoi velru’e zo’u crepu le plibu taxfu
.i le remoi velru’e zo’u mo .i le cimoi velru’e zo’u ba’e prali .uisai
http://www.lojban.org/ *** to sa’a cu’u lei pibyta’u cridrnoma toi

you’re trying to use RT 2.0 on Postgres 7.3. That’s not going to work.

Hmmm. That’s an aspect I hadn’t thought of: how much trouble am I in
when I try to upgrade to RT 3, since I’m runing 2.0 on PG 7.3?

If you’ve beaten 2.0 into submission, you should be ok, though there may
be more lurking atoi issues you haven’t found that the exporter
exercises.

-j

-Robin


http://www.digitalkingdom.org/~rlpowell/ *** I’m a male Robin.
.i le pamoi velru’e zo’u crepu le plibu taxfu
.i le remoi velru’e zo’u mo .i le cimoi velru’e zo’u ba’e prali .uisai
http://www.lojban.org/ *** to sa’a cu’u lei pibyta’u cridrnoma toi


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

-----BEGIN PGP SIGNED MESSAGE-----On 11-Mar-2003 Jesse Vincent wrote:

you’re trying to use RT 2.0 on Postgres 7.3. That’s not going to work.

Ok, installed pg7.2x, sucked in the sql dump from the other server’s rt2 db.
Used rt-2.0-to-dumpfile to create the rt dump. Started running the
dumpfile-to-rt-3.0 and it looked like it was going to work, but hit a snag.
Any clues on this one?

(my theory is that it’s just refusing to import an attachment with the word
’obtundent’ in it… :wink:

Importing ticket 102
transaction 571
attachment 401
transaction 572
attachment
[Wed Mar 12 14:17:41 2003] [crit]: Couldn’t create attachment HASH(0x8de0f0c)
$VAR1 = {
‘ContentType’ => ‘text/plain’,
‘Created’ => ‘2002-05-14 19:20:48+00’,
‘Content’ => '
Reported by : jds
Start time : 01/09/2002; 22:15:00
Duration : 01:15:00
Customers affected : all dialup
Service affected : "Network Connectivity"
Impact on service : Service unavailable
Trouble Contact : solunet?

Symptoms noticed/reported:
tc2 became obtundent. Could not reach over the network. After a manual
powercyc\
le, the tech attached to the console reported the tc repeatedly booting,
crashi\
ng, booting, etc.

jcoombs can provide more detail into the diagnosing of the device, as he was
th\
e one to work on it from the console server.

Problem resolved as follows:
It was determined that the CF on the ARC module was bad. I removed the ARC
mod.\
from tc5 and replaced the bad ARC with it. The bad ARC was then put into tc5.

This could be prevented as follows:
Have spares on site! That would have at least reduced the length and severity
o\
f the outage. I imagine that others in network can provide better analysis on
t\
his issue than I can. :slight_smile:

',
‘ContentEncoding’ => ‘none’,
‘Creator’ => ‘4’,
‘TransactionId’ => ‘572’
};
(/opt/rt3/lib/RT.pm:228)


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPm9DflPEkLgodAWVAQFLJAP/QbJ/Kxr+QEaswjgIF6pqfY1yJQ7qtBdE
RVC2IJIJ+0Qhd1dKBtF6GnjkHAV85o+AS8p/1mHFuEWXK38LPFw3bmkmFwGl49fE
1uSJXXQs5bqKofGl7VRgtMID8sJacFaQKZxNVoSuQXXuRMueaOosa4UdJeXz1gjw
uie3du6UGAg=
=njOc
-----END PGP SIGNATURE-----

Andy> rt2 db. Used rt-2.0-to-dumpfile to create the rt dump. Started
Andy> running the dumpfile-to-rt-3.0 and it looked like it was going to
Andy> work, but hit a snag. Any clues on this one?

Andy> (my theory is that it’s just refusing to import an attachment with
Andy> the word ‘obtundent’ in it… :wink:

The upgrade script doesn’t correctly quote the Content part for the
postgresql type bytea (I think \ needs to be \\ amoung other things).

One (evil) fix is to change the schema to use text instead of bytea

A related question: why is the new postgresql schema using bytea instead of
text (as it used to in 2.0.x) ?

Aaron

-----BEGIN PGP SIGNED MESSAGE-----On 12-Mar-2003 Aaron Wilson wrote:

The upgrade script doesn’t correctly quote the Content part for the
postgresql type bytea (I think \ needs to be \\ amoung other things).

One (evil) fix is to change the schema to use text instead of bytea

A related question: why is the new postgresql schema using bytea instead of
text (as it used to in 2.0.x) ?

Aaron

I went into the attachments table, dropped content and headers which showed
bytea, and recreated them as text.

Now it fails right at the first ticket instead of doing a bunch:

Importing ticket 1
transaction 1
attachment
[Wed Mar 12 16:21:39 2003] [crit]: Couldn’t create attachment HASH(0x8e7f30c)
$VAR1 = {
‘ContentType’ => ‘text/plain’,
‘Created’ => ‘2002-05-14 19:20:22+00’,
‘Content’ => ’

Time of incident:

IPs:

Usernames:

Traceroute:

',
‘ContentEncoding’ => ‘none’,
‘Creator’ => ‘4’,
‘TransactionId’ => ‘1’
};
(/opt/rt3/lib/RT.pm:228)


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPm9fZlPEkLgodAWVAQHQtgQAhjIXEgx4pw3tXwpAdoew8Z12gafFCFOI
Mp2e8Xun9bjGqtc35nFBfiUhYFJs3HfOB8G7FEbQ/zea6wrz8/+9SsDvPAYcfNmI
DYUdidnpArcNg10fR0EiwB7hEE/9ZiTMkFebyF9O0O0+XZU2IL1GVzs6AHvIHFn+
ypb1lQ+uM+k=
=ZxjV
-----END PGP SIGNATURE-----

Andy> rt2 db. Used rt-2.0-to-dumpfile to create the rt dump. Started
Andy> running the dumpfile-to-rt-3.0 and it looked like it was going to
Andy> work, but hit a snag. Any clues on this one?

Andy> (my theory is that it’s just refusing to import an attachment with
Andy> the word ‘obtundent’ in it… :wink:

The upgrade script doesn’t correctly quote the Content part for the
postgresql type bytea (I think \ needs to be \\ amoung other things).

Interesting. That sort of sounds like a bug in DBD::pgsql’s quoting
mechanism.

One (evil) fix is to change the schema to use text instead of bytea

A related question: why is the new postgresql schema using bytea instead of
text (as it used to in 2.0.x) ?

So that we can evenutally stop base-64 encoding all attachments.

Aaron


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

-----BEGIN PGP SIGNED MESSAGE-----


On 12-Mar-2003, Jesse Vincent wrote message “Re: [rt-users] 2.x > 3.x”


Interesting. That sort of sounds like a bug in DBD::pgsql’s quoting
mechanism.

Ok, I tried to get by this simply by removing the ticket files from the dump
directory that were causing problems. Now, after it’s finished with that part,
it starts spewing errors like this:

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Comment’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Correspond’
};

and also like this:

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/257’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 257,
‘Created’ => ‘2002-10-01 00:05:47+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:47+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/254’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 254,
‘Created’ => ‘2002-10-01 00:05:47+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:47+00’
};

Any ideas?


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPnHeXVPEkLgodAWVAQEFtAQAqnRbsG78NyBz0+S1IDZADgLH/Nh7l7Eu
3P3zATQN4CrGiNLFIFL7I+JEp/cxPsj7G4hHWC06OMJMblR049hzXd8WkOBUyx5S
x5ouTL1P9taznnN5P3NGuN/RJIXNm9QVoJGnVQODAmGAll/OrjG346Y1sjosvyfW
XnA/dCDJBS4=
=Hr0Q
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----


On 12-Mar-2003, Jesse Vincent wrote message “Re: [rt-users] 2.x > 3.x”


Andy> rt2 db. Used rt-2.0-to-dumpfile to create the rt dump. Started
Andy> running the dumpfile-to-rt-3.0 and it looked like it was going to
Andy> work, but hit a snag. Any clues on this one?

Andy> (my theory is that it’s just refusing to import an attachment with
Andy> the word ‘obtundent’ in it… :wink:

The upgrade script doesn’t correctly quote the Content part for the
postgresql type bytea (I think \ needs to be \\ amoung other things).

Interesting. That sort of sounds like a bug in DBD::pgsql’s quoting
mechanism.

Ok, just for fun, I went ahead and installed mysql and set it up (with
rt-2-1-87) and tried the import again. It only bombed out on 3 or 4 tickets
and they were 100000+ lines.

But after the last ticket was imported, it gave similar errors than when I
removed the “bad” tickets while importing into postgres.

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Comment’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Correspond’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Resolved’,
‘Condition’ => ‘On Resolve’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Correspond’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers’,
‘Template’ => ‘Resolved’,
‘Condition’ => ‘On Resolve’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers’,
‘Template’ => ‘Transaction’,
‘Condition’ => ‘On Create’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Comment’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Resolved’,
‘Condition’ => ‘On Resolve’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Correspond’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘escalation-resolved’,
‘Condition’ => ‘On Resolve’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Correspond’
};
Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify AdminCcs’,
‘Template’ => ‘Transaction’,
‘Condition’ => ‘On Status’
};

Could not create scrip: $VAR1 = {
‘Action’ => ‘Notify All Watchers As Comment’,
‘Template’ => ‘Correspondence’,
‘Condition’ => ‘On Correspond’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/257’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 257,
‘Created’ => ‘2002-10-01 00:05:47+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:47+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/254’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 254,
‘Created’ => ‘2002-10-01 00:05:47+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:47+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/247’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 247,
‘Created’ => ‘2002-10-01 00:05:47+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:47+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/245’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 245,
‘Created’ => ‘2002-10-01 00:05:47+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:47+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/242’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 242,
‘Created’ => ‘2002-10-01 00:05:48+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:48+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/240’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 240,
‘Created’ => ‘2002-10-01 00:05:48+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:48+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/239’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 239,
‘Created’ => ‘2002-10-01 00:05:48+00’,
‘LastUpdated’ => ‘2002-10-01 00:05:48+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/267’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 267,
‘Created’ => ‘2002-10-02 18:58:31+00’,
‘LastUpdated’ => ‘2002-10-02 18:58:31+00’
};

Couldn’t create link 255 appears to be a local object, but can’t be found in
the database$VAR1 = {
‘Target’ => ‘fsck.com-rt:/ticket/255’,
‘Base’ => ‘fsck.com-rt:/ticket/265’,
‘LocalTarget’ => 255,
‘Creator’ => ‘6’,
‘Type’ => ‘MemberOf’,
‘LastUpdatedBy’ => ‘6’,
‘LocalBase’ => 265,
‘Created’ => ‘2002-10-03 18:26:11+00’,
‘LastUpdated’ => ‘2002-10-03 18:26:11+00’
};


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPnXmdlPEkLgodAWVAQHDrwP/VDsjKaSj0PR4v4kASixIsrwgem9SoFz/
wVBXggvRlLci7VfGanwIDEsQklY/SzQFfIt+4CPhFlsxkRt5xniOfz0fkOmbW/rV
kb6aHcPNivJOqMP13crO6WArObiXRIUVgiEYxGUMCJGnObGtPOCrteUEf8mAqFa2
Q2OVuMmHcPU=
=hJ/3
-----END PGP SIGNATURE-----

At 12:40 PM 12/03/2003 -0500, Jesse Vincent wrote:

Interesting. That sort of sounds like a bug in DBD::pgsql’s quoting
mechanism.

There is a bug in there somewhere. The problem is that the DBD::Pg people
can’t think of a way to fix it transparently. The current suggestion is to
check if the driver is Pg, and use bind_param to specify { pg_type =>
DBD::Pg::PG_BYTEA } for those columns that you know are bytea. Which is
obviously a problem.

This is a problem in rc2, at least, since any message containing a
backslash will silently fail to be stored when sent through the mail gateway.

Philip Warner | ___
Albatross Consulting Pty. Ltd. |----/ -
(A.B.N. 75 008 659 498) | /(@)
Tel: (+61) 0500 83 82 81 | _________
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / |
| –
___–
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

-----BEGIN PGP SIGNED MESSAGE-----


On 19-Mar-2003, Philip Warner wrote message “Re: [rt-users] 2.x > 3.x”


can’t think of a way to fix it transparently. The current suggestion is to
check if the driver is Pg, and use bind_param to specify { pg_type =>
DBD::Pg::PG_BYTEA } for those columns that you know are bytea. Which is

Could you elaborate on this a little more? What driver? And I know which
columns are bytea, but i’m not sure what you’re saying to do with bind_param.
I searched for bind_param and pg_type in my rt download dir (which is where my
rt2 dump is also), didn’t come up with anything.


Andy Harrison
Great Works Internet
System Operations
ajharrison@gwi.net
RSA 1024 pgp key: http://www.nachoz.com/andy.pub

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

iQCVAwUBPnh34VPEkLgodAWVAQFIfAP/WkKh2zSJUDfpkWrqYMindLeuSVj81v34
iBicC4G9B0Dy0psG5o6dImF/EU2BjvusE0hatxOdQtcVH8vjOFPxdQnIDhfwIWvw
Kqc7IEr1ogaqRRKEcTsxgz+HwXkdFVnonmRUo8p7l9h+eDLF5B77WI5s+jFhn2By
6FSC7Fuj46w=
=VpQk
-----END PGP SIGNATURE-----