Hello Everyone,
I am posting this to let you all know about a problem I was having and the
solution.
Problem:
Running 2.0.8pre3 (from CVS) or 2.0.7 of RT, using Postgresql (7.0 series),
and are having problems with a bug submitted not showing up in the user’s
home page top 25 requested list.
As a side note, whenever I add the requestor to a query, I get NO results,
even if I can see in the list the requestor I want. For example, I select
to see all new items in a queue. Looking at the list, a choose a requestor
from the Requestor(s) column and add an additional query for it (using
either is or contains). I no longer get anything 
Solution:
After some log scans and responses w/ Jesse, came to the conclusion this was
due to the handling of outer joins in the SQL passed to Postgresql. By
upgrading to the 7.1 series of Postgresql (7.1.3 actually), the problem went
away (7.1 has changed the way it handles the syntax for outer joins).
So, if you’re running postgres prior to 7.1, I would recommend an upgrade 
Enjoy!
Michael Huttinger
Computer Engineer
IPACT
web: http://www.ipact.com
In fact, I discovered recently that Postgres versions before 7.1 did not
support one of the join types that RT needs. Expect 2.0.9 to note the hard
requirement for 7.1. Oh. wait. I already do. Better make sure that’s true
everywhere.On Tue, Oct 02, 2001 at 07:26:50AM -0500, Michael Huttinger wrote:
Hello Everyone,
I am posting this to let you all know about a problem I was having and the
solution.
Problem:
Running 2.0.8pre3 (from CVS) or 2.0.7 of RT, using Postgresql (7.0 series),
and are having problems with a bug submitted not showing up in the user’s
home page top 25 requested list.
As a side note, whenever I add the requestor to a query, I get NO results,
even if I can see in the list the requestor I want. For example, I select
to see all new items in a queue. Looking at the list, a choose a requestor
from the Requestor(s) column and add an additional query for it (using
either is or contains). I no longer get anything
Solution:
After some log scans and responses w/ Jesse, came to the conclusion this was
due to the handling of outer joins in the SQL passed to Postgresql. By
upgrading to the 7.1 series of Postgresql (7.1.3 actually), the problem went
away (7.1 has changed the way it handles the syntax for outer joins).
So, if you’re running postgres prior to 7.1, I would recommend an upgrade
Enjoy!
Michael Huttinger
Computer Engineer
IPACT
web: http://www.ipact.com
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.
A word to the wise, the file structure for 7.1 changed radically from earlier versions, although there is a configure option to use ‘old-style-layout’. I’d advise keeping your old installation live, until you’ve ensured you can import the older data into 7.1 - there are (were?) some problems importing dumps from earlier versions.
FWIW, RT’s README has stated version 7.1 for postgres since at least 1.3.30, so hopefully it doesn’t affect too many people.
-Feargal.“Michael Huttinger” huttinger@ipact.com wrote:
MH> Hello Everyone,
MH>
MH> I am posting this to let you all know about a problem I was having and the
MH> solution.
MH>
MH> Problem:
MH>
MH> Running 2.0.8pre3 (from CVS) or 2.0.7 of RT, using Postgresql (7.0 series),
MH> and are having problems with a bug submitted not showing up in the user’s
MH> home page top 25 requested list.
MH>
MH> As a side note, whenever I add the requestor to a query, I get NO results,
MH> even if I can see in the list the requestor I want. For example, I select
MH> to see all new items in a queue. Looking at the list, a choose a requestor
MH> from the Requestor(s) column and add an additional query for it (using
MH> either is or contains). I no longer get anything
MH>
MH> Solution:
MH>
MH> After some log scans and responses w/ Jesse, came to the conclusion this was
MH> due to the handling of outer joins in the SQL passed to Postgresql. By
MH> upgrading to the 7.1 series of Postgresql (7.1.3 actually), the problem went
MH> away (7.1 has changed the way it handles the syntax for outer joins).
MH>
MH> So, if you’re running postgres prior to 7.1, I would recommend an upgrade
MH>
MH> Enjoy!
MH>
MH> Michael Huttinger
MH> Computer Engineer
MH> IPACT
MH> web: http://www.ipact.com
MH>
MH>
MH> _______________________________________________
MH> rt-users mailing list
MH> rt-users@lists.fsck.com
MH> http://lists.fsck.com/mailman/listinfo/rt-users
MH>
Feargal Reilly,
Systems Administrator,
The CIA.
“MH” == Michael Huttinger huttinger@ipact.com writes:
MH> So, if you’re running postgres prior to 7.1, I would recommend an
MH> upgrade
You’ll probably also lose data for tickets that are larger than 8k
unless you’re using 7.1.x.