Before we spring hstore on an unsuspecting world as a contrib module, in
the interests of good English, is it too late to change "isexists" to
simply "exists"?

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Andrew Dunstan wrote:
>
> Before we spring hstore on an unsuspecting world as a contrib module, in
> the interests of good English, is it too late to change "isexists" to
> simply "exists"?

Sure, we can do it, as long as we aren't worried about adding
incompatibilities for existing hstore users.

--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

It's possible to create function 'exists' and mention only it in docs.

Bruce Momjian wrote:
> Andrew Dunstan wrote:
>> Before we spring hstore on an unsuspecting world as a contrib module, in
>> the interests of good English, is it too late to change "isexists" to
>> simply "exists"?
>
> Sure, we can do it, as long as we aren't worried about adding
> incompatibilities for existing hstore users.
>

--
Teodor Sigaev E-mail: teodor@sigaev.ru
WWW: http://www.sigaev.ru/

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Teodor Sigaev wrote:
> It's possible to create function 'exists' and mention only it in docs.

Good point. Will you do that, or do you want me to?


>
> Bruce Momjian wrote:
>> Andrew Dunstan wrote:
>>> Before we spring hstore on an unsuspecting world as a contrib
>>> module, in the interests of good English, is it too late to change
>>> "isexists" to simply "exists"?
>>
>> Sure, we can do it, as long as we aren't worried about adding
>> incompatibilities for existing hstore users.
>>
>

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Andrew Dunstan wrote:
> Teodor Sigaev wrote:
>> It's possible to create function 'exists' and mention only it in docs.
>
> Good point. Will you do that, or do you want me to?

May I ask you? I'm afraid that there is more incorrectness.


--
Teodor Sigaev E-mail: teodor@sigaev.ru
WWW: http://www.sigaev.ru/

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Teodor Sigaev wrote:
>
>
> Andrew Dunstan wrote:
>> Teodor Sigaev wrote:
>>> It's possible to create function 'exists' and mention only it in docs.
>>
>> Good point. Will you do that, or do you want me to?
>
> May I ask you? I'm afraid that there is more incorrectness.
>
>

Well, "isdefined" isn't incorrect, but I think there's a good case to
change it to just "defined", since exists and defined are the names of
the corresponding perl tests on associative arrays. All the rest look ok
to me.

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

'exists' isn't a good name for function . From gram.y:
col_name_keyword:
...

function_name:
IDENT { $$ = $1; }
| unreserved_keyword { $$ = pstrdup($1); }
| func_name_keyword { $$ = pstrdup($1); }
;

So call of function named 'exists' should be in quotas:
select "exists"('a=>1','a');

--
Teodor Sigaev E-mail: teodor@sigaev.ru
WWW: http://www.sigaev.ru/

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Teodor Sigaev <teodor@sigaev.ru> writes:
> 'exists' isn't a good name for function .

Yeah, that isn't going to work. Perhaps "ifexists"? Or just leave well
enough alone.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Tom Lane wrote:
> Teodor Sigaev <teodor@sigaev.ru> writes:
>
>> 'exists' isn't a good name for function .
>>
>
> Yeah, that isn't going to work. Perhaps "ifexists"? Or just leave well
> enough alone.
>
>
>

Darn. Can't have been thinking clearly this morning.

How about "exist" (no s)?

cheers

andrew




---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Andrew Dunstan <andrew@dunslane.net> writes:
> How about "exist" (no s)?

Seems a bit ugly, but better than isexists or ifexists ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster