Thread

Re: [HACKERS] Re: varchar() troubles

Keith Parks <emkxp01@mtcc.demon.co.uk> — 1998-01-19T18:52:52Z

Thanks Bruce,

It was obviously not quite as simple a problem as I had 1st imagined.

I did have a root around in the code but could not work out how the
attributes were copied to the newly created table.

Thanks for the fix,
Keith.

Bruce Momjian <maillist@candle.pha.pa.us>
> emkxp01@mtcc.demon.co.uk
> > Bruce,
> > 
> > The new varchar() stuff looks good, just a minor problem with "select into"
> > where the new table does not seem to get a copy of the atttypmod value
> > from the source table.
> > 
> > I had a quick look at the code but guess you'll find the problem 10 times
> > faster than I could.
> 
> OK, I have fixed this.  The real way to fix this it to add restypmod to
> Resdom, and pass the value all the way through the engine, so tupDesc
> always has the proper atttypmod value, but it is not clear how to do
> this in the parser, so I put the code back in to just do a lookup in
> execMain/execUtils when doing an SELECT * INTO TABLE.
> 
> If we start using atttypmod more, we will have to do this.
>