| From: | Russ Brown <pickscrape(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL sequence within function |
| Date: | 2005-07-01 06:33:26 |
| Message-ID: | 42C4E3B6.50800@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tony Caduto wrote:
> All you where really mising was a semi colon afer nextval('myseq') and
> the begin end.
>
> CREATE or REPLACE FUNCTION getSeq()
> RETURNS int AS
> $$
> begin
> RETURN nextval('myseq');
> end;
> $$
> LANGUAGE 'plpgsql';
>
> Clark Allan wrote:
>
This just made me think. If I was writing this function, I would have
written it as an SQL function like this:
CREATE or REPLACE FUNCTION getSeq() RETURNS int AS $$
SELECT nextval('myseq');
$$ LANGUAGE SQL;
Does anybody know which version is actually better/faster/more optimal?
I tend to always write functions as SQL where it's possible, as I
imagine that an SQL database engine will be better at running an SQL
functionion than an interpreted procedural function. Am I right to think
that?
--
Russ.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Russ Brown | 2005-07-01 06:48:55 | Re: COnsidering a move away from Postgres |
| Previous Message | Christopher Kings-Lynne | 2005-07-01 04:12:09 | Re: [ANNOUNCE] Language to use with SQL database - Number |