[Rt-devel] rt3-schema-relationships.dot out of date?

Jesse Vincent jesse at bestpractical.com
Fri Nov 11 00:07:37 EST 2005




On Fri, Nov 11, 2005 at 12:42:03AM -0500, Todd Chapman wrote:
> On Thu, Nov 10, 2005 at 11:56:58PM -0500, Jesse Vincent wrote:
> > 
> > 
> > 
> > On Thu, Nov 10, 2005 at 02:54:26PM -0500, Todd Chapman wrote:
> > > On Thu, Nov 10, 2005 at 01:22:17PM -0500, Jesse Vincent wrote:
> > > > 
> > > > > > No. Links are either tied directly to tickets or to arbitrary URIs.
> > > > > > 
> > > > > 
> > > > > Am I correct in understanding that the links to arbitrary URLs
> > > > > were added later, and that links directly to tickets is more
> > > > > of a backwards compatability thing?
> > > > 
> > > > Nope. It's a "and you can't easily build joins between a ticket id and a
> > > > URL" thing.
> > > 
> > > Or between two URL things... right?
> > 
> > 
> > Huh? It's easy to join on string equality. but joining a ticket id to a
> > URL isn't doable.  The way we've solved this for RTFM is to contrive the
> > full URI for an article and store it in the Articles table. Which
> > doesn't make me really happy.
> > 
> 
> At this point I'm not sure if we are talking past each other.
> What I am trying to do is understand if I am mis-using links
> in Asset Tracker, where I have been successfully using Link
> to define relationships between assets, as well as between
> assets and tickets.

Right. that's absolutely fine. I was talking about not being able to do
a JOIN in the database between a URI and an integer.

> -Todd
> 

-- 


More information about the Rt-devel mailing list