On Fri, Aug 19, 2005 at 15:15:44 +0100,
Nigel Horne <[EMAIL PROTECTED]> wrote:
> Thanks for all the pointers. I'll have a look. I did reply
> earlier, but the "reply to" is broken: it sent to the OP
> rather than the list...
No it isn't broken. You should use the reply to all function of your ma
Thanks for all the pointers. I'll have a look. I did reply
earlier, but the "reply to" is broken: it sent to the OP
rather than the list...
Perhaps there is a lesson in newbie navigation for the
website here.
-Nigel
---(end of broadcast)---
TIP 1:
Nigel Horne <[EMAIL PROTECTED]> writes:
> The on-line manual,
> http://www.postgresql.org/docs/8.0/interactive/index.html,
> doesn't describe how to call stored functions, or if it does
> it's well hidden.
Start here:
http://www.postgresql.org/docs/8.0/static/xfunc.html
http://www.postgresql.org/d
Nigel Horne schrieb:
The on-line manual,
http://www.postgresql.org/docs/8.0/interactive/index.html,
doesn't describe how to call stored functions, or if it does
it's well hidden.
Are there some examples anywhere? After
googling I can find much duplication of non-data (people
love to mirror sites
On Fri, Aug 19, 2005 at 12:07:57PM +0100, Nigel Horne wrote:
> The on-line manual,
> http://www.postgresql.org/docs/8.0/interactive/index.html,
> doesn't describe how to call stored functions, or if it does
> it's well hidden.
>
> Are there some examples anywhere? After
> googling I can find much
am 19.08.2005, um 12:07:57 +0100 mailte Nigel Horne folgendes:
> The on-line manual,
> http://www.postgresql.org/docs/8.0/interactive/index.html,
> doesn't describe how to call stored functions, or if it does
> it's well hidden.
test=# create function get_foobar () returns varchar as $$begin retu
The on-line manual,
http://www.postgresql.org/docs/8.0/interactive/index.html,
doesn't describe how to call stored functions, or if it does
it's well hidden.
Are there some examples anywhere? After
googling I can find much duplication of non-data (people
love to mirror sites don't they?) but no re
Thats most of what I needed. I shouls be able to suss out the rest.
Thanks
Rick
Martijn van Oosterhout wrote:
Well, using the -E option to psql, \df expands to:
SELECT CASE WHEN p.proretset THEN 'setof ' ELSE '' END ||
pg_catalog.format_type(p.prorettype, NULL) as "Result data type",
n.nspna
Well, using the -E option to psql, \df expands to:
SELECT CASE WHEN p.proretset THEN 'setof ' ELSE '' END ||
pg_catalog.format_type(p.prorettype, NULL) as "Result data type",
n.nspname as "Schema",
p.proname as "Name",
pg_catalog.oidvectortypes(p.proargtypes) as "Argument data types"
FROM
select * from pg_proc where proname = ''
Sincerely,
Joshua D. Drake
Rich Hall wrote:
Thanks for the psql response.
But, I seldom use psql. I find PG Manager much more useful. Even PG
Admin was better.
I am looking to write some stored functions to query the database to
automatically create
Thanks for the psql response.
But, I seldom use psql. I find PG Manager much more useful. Even PG
Admin was better.
I am looking to write some stored functions to query the database to
automatically create the repotrs I now generate by hand.
So I was trying to find my Stored Functions in the da
On Fri, Dec 05, 2003 at 02:22:26PM -0500, Rich Hall wrote:
> Can somebody tell me how Stored Functions are kept in the database? I've
> gone through the catalog several times. I've found many interesting
> things but NOT the 300-odd functions I've created.
>
> Rick
\df
--
Martijn van Oosterho
Can somebody tell me how Stored Functions are kept in the database? I've
gone through the catalog several times. I've found many interesting
things but NOT the 300-odd functions I've created.
Rick
--
---(end of broadcast)---
TIP 3: if posting/r
13 matches
Mail list logo
