From: Edmund Bacon <ebacon@onesystem.com>
To: wespvp@syntegra.com
Cc: pgsql-interfaces@postgresql.org
Subject: Re: NULLs in ecpg
Date: Fri, 16 Jul 2004 10:39:19 -0600
Message-ID: <40F804B7.2090101@onesystem.com> (raw)
In-Reply-To: <BD1D6BC7.F3B8%wespvp@syntegra.com>
References: <BD1D6BC7.F3B8%wespvp@syntegra.com>
wespvp@syntegra.com wrote:
> On 7/16/04 11:11 AM, "Edmund Bacon" <ebacon@onesystem.com> wrote:
>
>
>>Indicators works as expected. e.g.:
>>
>>EXEC SQL INSERT INTO sometable
>> VALUES (:v1 :v1_ind, 'foo', :v2 :v2_ind);
>
>
> Hmm. I tried that. Just tried it again and it worked. Must have had a
> typo before. Sorry.
>
> What about if I have something like:
>
> ... VALUES (TO_TIMESTAMP(:expirationDate, 'YYYYMMDDHH24MISS'), 'foo', :v2)
>
> How can I insert NULLS for expirationDate when there's a function in the
> way? Using
>
> ... VALUES (TO_TIMESTAMP(:expirationDate, 'YYYYMMDDHH24MISS') :ind1, ...
>
> won't work.
No, but
... VALUES (TO_TIMESTAMP(:expirationDate :ind1, 'YYYYMMDDHH24MISS'), ..
should
--
Edmund Bacon <ebacon@onesystem.com>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ebacon@onesystem.com, wespvp@syntegra.com
Subject: Re: NULLs in ecpg
In-Reply-To: <40F804B7.2090101@onesystem.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox