| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Aasmund Midttun Godal" <postgresql(at)envisity(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Variables. |
| Date: | 2001-10-17 15:44:44 |
| Message-ID: | web-149639@davinci.ethosmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Aasmund,
> I do not know whether it is part of the SQL standard.
>
> Variables...
Nope.
> CREATE VARIABLE foobar INTEGER DEFAULT 1 NOT NULL;
>
> SELECT * FROM thebar WHERE id = foobar;
>
> CREATE TEMPORARY VARIABLE...
> CREATE CONSTANT....
Extensive support for a variety of variable types and constructions is
available in FUNCTIONS. PL/pgSQL, PL/TCL, PL/Perl ... take your pick.
For the raw command-line SQL, variables, constants, and other procedural
language elements are not appropriate. This is best done in procedures,
functions, and middleware.
Of course, it is an Open-Source project, so if you hire your own
programmer, you can do anything you want.
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| unknown_filename | text/plain | 2 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haller Christoph | 2001-10-17 17:17:44 | Identifying obsolete values |
| Previous Message | Josh Berkus | 2001-10-17 15:40:32 | Re: Performance problems - Indexes and VACUUM |