Re: [HACKERS] Re: [QUESTIONS] impossible insert data into VARCHAR

From: jwieck(at)debis(dot)com (Jan Wieck)
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart)
Cc: jwieck(at)debis(dot)com, sferac(at)bo(dot)nettuno(dot)it, hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: [QUESTIONS] impossible insert data into VARCHAR
Date: 1998-02-05 16:54:14
Message-ID: m0y0UZ5-000BFRC@orion.SAPserv.Hamburg.dsh.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Jan Wieck wrote:
>
> > > [... quoting level exceeded ...]
> >
> > ARRRRG - then next problem with VARSIZE - damn thing.
> >
> > This time it's during the parser (gdb told me). varcharin()
> > is called with a atttypmod of 0 causing a palloc() of 0
> > bytes. How should a VARCHAR type whithout a specified length
> > behave? Is this type 1 character or a variable size up to
> > 4096?
>
> It should allow any length (up to the implementation maximum of 4096). The usage is not defined for SQL92,
> unlike the case for "char" with no explicit size which defaults to one.
>

Could be hacked into varcharin(). If the test on atttypmod is
changed from "!= -1" into "> 0" it works that way. Don't
have the time right now to run a regression test, but some
typed queries with

select into t values ...

and

select into t select ...

worked O.K.

Until later, Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ewan Mellor 1998-02-05 17:00:15 create function bug?
Previous Message Bruce Momjian 1998-02-05 16:50:31 Re: [HACKERS] Bug?