[rt-devel] RT 2.0.14-pre1

[Jesse Vincent]

It seems to me like the lightest-weight solution here is to create and 
document an alternate pg 7.2+ schema for RT 2.0.x and create a similar
schema for the 2.1.x series as the "native" pg schema.

Slightly longer term is to drop a proper exception system into DBIx::SearchBuilder so that it can cope cleanly.

	-j


On Mon, Jul 01, 2002 at 08:19:10PM +0200, Florian Weimer wrote:
> Vivek Khera <khera at kcilink.com> writes:
> 
> > I think text == varchar(2^24-1) or something about like that.  My
> > feeling is that varchar() of a given size is mainly for documenting
> > your structure and expected use.  The data storage is not that
> > different.  Perhaps you save a byte or two by having smaller length
> > counters for shorter varchars, but I don't know.
> 
> Some people claim that internally, a TEXT column is represented by an
> offset into a different table, but this is not the case, at least if
> a row stays below the TOAST limit (somewhere around 8 kilobytes).
> 
> -- 
> Florian Weimer 	                  Weimer at CERT.Uni-Stuttgart.DE
> University of Stuttgart           http://CERT.Uni-Stuttgart.DE/people/fw/
> RUS-CERT                          fax +49-711-685-5898
> 

-- 
http://www.bestpractical.com/products/rt  -- Trouble Ticketing. Free.