Re: PostgresQL equivalent of NOCOUNT - Mailing list pgsql-general

From Dwayne Miller
Subject Re: PostgresQL equivalent of NOCOUNT
Date
Msg-id 3B79C0C7.1090102@espgroup.net
Whole thread Raw
In response to PostgresQL equivalent of NOCOUNT  (Jochem van Dieten <jochemd@oli.tudelft.nl>)
List pgsql-general

Jochem van Dieten wrote:

> Dwayne Miller wrote:
>
>>
>> SELECT nextval('mysequence') AS PKEY FROM DUAL;
>> ...
>> Your inserts and updates using #queryname.pkey#
>
>
> I know, but it has 2 queries again, which is exactly the reason why I
> don't want it (I am actually developing this to be used by others).
> BTW, you can just call functions without a FROM, as in:
> SELECT now() AS test

Not very portable... which was a requirement for me.

I generally have to use the same key in a series of 1 to 3 inserts, so
this solution seems to work well.

>
>> One solution of many
>
>
> I think I will just replace cfquery with cf_query. Then have cf_query
> replace every insert with a function call (so I don't have to double
> all the quotes manually), where the function takes care about the rest
> and returns #insertedrecord.id# or whatever. Would probably be the
> easiest way to explain to others.
>
> Jochem
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl




pgsql-general by date:

Previous
From: Joseph Shraibman
Date:
Subject: dump/restore failing in 7.1.2
Next
From: Geoffrey Gallaway
Date:
Subject: Re: PGSQL Intro & Concepts PDF