| From: | Felipe Schnack <felipes(at)ritterdosreis(dot)br> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: EXECUTE problems |
| Date: | 2002-11-22 16:46:14 |
| Message-ID: | 1037983574.14866.42.camel@desenv1.ritterdosreis.br |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
No, no... in pgsql 7.3 you can do "insert into test (columnName)
values (DEFAULT)" and it works! It just doesn't work for prepared
statements. Maybe I should join the pgsql-developers list?
On Fri, 2002-11-22 at 14:45, Neil Conway wrote:
> Felipe Schnack <felipes(at)ritterdosreis(dot)br> writes:
> > Yes, I did... sorry, the error message was "parser: parse error at
> > or near "default" at character 26". Seems to me that execute doesn't
> > "know" DEFAULT keyrword?
>
> Yeah, the handling of the DEFAULT keyword is currently done within the
> parsing of the INSERT statement itself. Not sure if that should be
> changed...
>
> You can insert the default value into a column by excluding it from
> the column list in the INSERT statement -- that should work for you
> here...
>
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
>
--
Felipe Schnack
Analista de Sistemas
felipes(at)ritterdosreis(dot)br
Cel.: (51)91287530
Linux Counter #281893
Faculdade Ritter dos Reis
www.ritterdosreis.br
felipes(at)ritterdosreis(dot)br
Fone/Fax.: (51)32303328
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-11-22 16:53:05 | Re: Lack of use of indexes |
| Previous Message | Neil Conway | 2002-11-22 16:45:21 | Re: EXECUTE problems |