Database tables


#1

Hi

I’m creating a search page that will search RT tickets. It currently
searches in the keywords and subject fields from each_req. I would like to
know where the comments and correspondence are stored so I can search
those fields too.

Thanks
SJS

Steve Sobol, BOFH, President 888.480.4NET 866.DSL.EXPRESS 216.619.2NET
North Shore Technologies Corporation http://NorthShoreTechnologies.net
JustTheNet/JustTheNet EXPRESS DSL (ISP Services) http://JustThe.net
mailto:sjsobol@NorthShoreTechnologies.net Proud resident of Cleveland, OH


#2

| I’m creating a search page that will search RT tickets. It currently
| searches in the keywords and subject fields from each_req. I would like to
| know where the comments and correspondence are stored so I can search
| those fields too.
±–>8

Howdy stranger :slight_smile:

If RT is installed in /home/rt, transaction text is found in
/home/rt/transactions/(year)/(month)/(day)/(serial_num).(transaction_id).

brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [“better check the oblivious first” -ke6sls]


#3

If RT is installed in /home/rt, transaction text is found in
/home/rt/transactions/(year)/(month)/(day)/(serial_num).(transaction_id).

Ick. How in $DEITY’s name are you supposed to do a SQL query on a
bunch of flat files?

shudder

That is incredibly, horrifically ugly. Someone please tell me that
that, um, feature will be fixed in 2.0.

Thanks, Brandon. :slight_smile:

Cheers, SJS.

Steve Sobol, BOFH, President 888.480.4NET 866.DSL.EXPRESS 216.619.2NET
North Shore Technologies Corporation http://NorthShoreTechnologies.net
JustTheNet/JustTheNet EXPRESS DSL (ISP Services) http://JustThe.net
mailto:sjsobol@NorthShoreTechnologies.net Proud resident of Cleveland, OH


#4

| Ick. How in $DEITY’s name are you supposed to do a SQL query on a
| bunch of flat files?
|
| shudder
|
| That is incredibly, horrifically ugly. Someone please tell me that
| that, um, feature will be fixed in 2.0.
±–>8

It is. RT1 was originally hampered by lame TEXT/BLOB support in early
MySQL, I believe.

brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [“better check the oblivious first” -ke6sls]


#5

±----
| That is incredibly, horrifically ugly. Someone please tell me that
| that, um, feature will be fixed in 2.0.
±–>8

It is. RT1 was originally hampered by lame TEXT/BLOB support in early
MySQL, I believe.

Actually, RT1 was hampered by the fact that at the time it was written, the only
free SQL database was Hughs miniSQL which didn’t support any sort of field
longer than ~256 bytes iirc.

RT2 stores things in blobs…which works fine with modern mysql revs.
The fact that postgres 7.1 doesn’t yet support 8bit-safe blobs is rather
a bummer.


brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [“better check the oblivious first” -ke6sls]


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

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

“Bother,” said Pooh, “Eeyore, ready two photon torpedoes and lock
phasers on the Heffalump, Piglet, meet me in transporter room three”


#6

I’m creating a search page that will search RT tickets. It currently
searches in the keywords and subject fields from each_req. I would like to
know where the comments and correspondence are stored so I can search
those fields too.

Ooooo, yes please. You will release it to the public, please
pretty please?

#include <std_disclaim.h> Lorens Kockum


#7

Hi

I’m creating a search page that will search RT tickets. It currently
searches in the keywords and subject fields from each_req. I would like to
know where the comments and correspondence are stored so I can search
those fields too.

Thanks
SJS

We actually try another kind - you need:

  • a standard web search engine, which could search only one level deep
  • a web access for that scanning engine (I’ve made a modification of
    rt.cgi let say rtview.cgi which is authenticated as an user with Display
    rights to requested RT queues.
  • a script calling rtstarted by cron before the search engine which
    generates one special index page searched by the engine - it contains only
    references to separated tickets.
    Here is an stupid examle:
    #!/usr/bin/perl
    $BASEURL=“http://your.url/rtview.cgi?display=History&serial_num=”;
    open(FIN,“cd /opt/rt/bin;./rtq -format “%n” -resolved -stalled -open
    -dead|”)
    ;
    while ()
    {
    if ($_ =~ /—/)
    {
    $start=1;
    next;
    }
    next unless $start;
    print “<A HREF=”$BASEURL$">$";
    }
    close(FIN);


Steve Sobol, BOFH, President 888.480.4NET 866.DSL.EXPRESS 216.619.2NET
North Shore Technologies Corporation http://NorthShoreTechnologies.net
JustTheNet/JustTheNet EXPRESS DSL (ISP Services) http://JustThe.net
mailto:sjsobol@NorthShoreTechnologies.net Proud resident of Cleveland, OH


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

Jan Okrouhly
-----------------------------------------±----okrouhly@civ.zcu.cz—
Laboratory for Computer Science | phone: (420 19) 7491588
University of West Bohemia | location: Univerzitni 22
Americka 42, 306 14 Pilsen, Czech Republic | room: UI404
------------------------------------------73!-de-OK1INC@OK0PPL.#BOH.CZE.EU-