Re: psql - user defined SQL variables

From: David Fetter <david(at)fetter(dot)org>
To: Grainne Reilly <greilly1(at)comcast(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: psql - user defined SQL variables
Date: 2004-08-18 05:48:43
Message-ID: 20040818054843.GN17886@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Aug 18, 2004 at 12:22:27AM -0400, Grainne Reilly wrote:
> I am new to PostgreSQL and am porting some scripts written for MySQL
> over to psql.

The least work you'll do here is to refactor your app entirely.

PostgreSQL will just plain handle about 3/4 of what you used to have
to deal with up in middleware land. It also supports all kinds of
wizardry that will astound you as you run across it. :)

> There is one MySQL feature which I cannot find in psql - user
> defined SQL variables. In MySQL I can use these to hold the result
> (numeric, string or null) of a select: e.g. select @count =
> count(*) from mytable;

This is a MySQLism to work around their lack of subselects. But if
that turns out not to be enough, you have a broad choice of procedural
languages, from the ADA-like PL/PgSQL to PL/Perl, PL/Python and (soon)
PL/PHP.

> Thanks in advance for any suggestions,

See about redoing your app. It will be less work than trying to graft
the MySQL design onto PostgreSQL, which is about like trying to hook
an ox cart to a jet engine :)

Cheers,
D
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778

Remember to vote!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Paramveer.Singh 2004-08-18 06:21:44 Re: exception handling support in pgSQL
Previous Message Tino Wildenhain 2004-08-18 05:28:17 Re: psql - user defined SQL variables