Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 6BDD92E0060 for ; Fri, 15 Feb 2008 06:38:03 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61358-05 for ; Fri, 15 Feb 2008 06:38:00 -0400 (AST) Received: from interscan.indicator.com (mail.indicator.be [193.121.199.3]) by postgresql.org (Postfix) with ESMTP id 831132E002C for ; Fri, 15 Feb 2008 06:37:59 -0400 (AST) Received: from DOMEXT-MTA by webaccess.indicator.bewith Novell_GroupWise; Fri, 15 Feb 2008 11:37:56 +0100 Message-Id: <47B5798B.A3DD.0030.0@indicator.be> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Fri, 15 Feb 2008 11:37:47 +0100 From: "Bart Degryse" To: "PostgreSQL SQL List" Cc: "Richard Huxton" Subject: Re: Function description References: <47B56063.A3DD.0030.0@indicator.be><47B556E6.8090200@archonet.co m><47B56F0B.A3DD.0030.0@indicator.be> <47B56651.9050600@archonet.com> In-Reply-To: <47B56651.9050600@archonet.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part9ABC656B.1__=" X-imss-version: 2.049 X-imss-result: Passed X-imss-approveListMatch: *@indicator.be X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/118 X-Sequence-Number: 30209 --=__Part9ABC656B.1__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable >>> Richard Huxton 2008-02-15 11:15 >>> >Dont' forget to cc: the list Bart :-) =20 My mistake, sorry. Normally I only reply to the list and not to the = respondent's personal address. Would that be wrong too? > >Bart Degryse wrote: >> Thanks for that explanation Richard. >> But how can I know what they repeat without having documentation. >> I mean, how about functions like eg regexeqjoinsel, regexeqsel, = reltimeeq, reltimege. >> I can imagine they mimic some other functionality, but how can I know = whichone? > >Well, like I said many implement operators, so they can be obviously = be=20 >found in pg_operator: > >SELECT * FROM pg_operator WHERE oprcode =3D 'reltimeeq'::regproc; Ok, now I see. Basically, something like this was what I was looking for. =20 > >The oprleft/right/result columns hold oid numbers for types in pg_type. > >Casts are listed in pg_cast etc. > >The fine manuals detail the system catalogues in a chapter "System=20 >Catalogs". >http://www.postgresql.org/docs/8.3/static/catalogs.html=20 I will take a close look at these. =20 > >To see how e.g. \dC etc work start psql with -E > I'm sorry, but I don't have commandline access to the database. That would require an amount of trust and a level of competence our ICT department is = incapable of. =20 >If it's not documented though, you need to ask two questions: >1. Why am I using it? =20 Well, at this moment I'm not using any of these functions as I didn't know = what they do. You have to admit though that it would by useless to implement = some functionality myself that already exists, but that I just didn't know = about because=20 I couldn't find it in the manual. Now I know there's only "aliases" to be found, no "undocument treasures". >2. Will it be there in the next version? > >--=20 > Richard Huxton > Archonet Ltd --=__Part9ABC656B.1__= Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Description: HTML

>>> Richard Huxton <dev@archonet.com> 2008-02-15 11:15 = >>>
>Dont' forget to cc: the list Bart :-)

My mistake, sorry. Normally I only reply to the list and not to the = respondent's personal address.

Would that be wrong too?

>
>Bart Degryse wrote:
>> Thanks for that = explanation Richard.
>> But how can I know what they repeat = without having documentation.
>> I mean, how about functions like = eg regexeqjoinsel, regexeqsel, reltimeeq, reltimege.
>> I can = imagine they mimic some other functionality, but how can I know whichone?>
>Well, like I said many implement operators, so they can be = obviously be
>found in pg_operator:
>
>SELECT * FROM = pg_operator WHERE oprcode =3D 'reltimeeq'::regproc;

Ok, now I see. Basically, something like this was what I was = looking for.

>
>The oprleft/right/result columns hold oid numbers for = types in pg_type.
>
>Casts are listed in pg_cast etc.
>>The fine manuals detail the system catalogues in a chapter "System =
>Catalogs".
>http://www.postgresql.org/docs/8.3/static/catalogs.html<= /A>

I will take a close look at these.

>
>To see how e.g. \dC etc work start psql with -E
>

I'm sorry, but I don't have commandline access to the database. That = would

require an amount of trust and a level of competence our ICT = department is incapable of.

>If it's not documented though, you need to ask two questions:
&= gt;1. Why am I using it?

Well, at this moment I'm not using any of these functions as I didn't = know what

they do. You have to admit though that it would by useless to = implement some

functionality myself that already exists, but that I just didn't know = about because

I couldn't find it in the manual.

Now I know there's only "aliases" to be found, no "undocument = treasures".

>2. Will it be there in the next version?
>
>-- =
> Richard Huxton
> Archonet Ltd
--=__Part9ABC656B.1__=--