From: | Jerome Slangen <jslangen(at)exmachina(dot)net> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | vijayendra mohan agrawal <vijayendra(dot)agrawal(at)wipro(dot)com>, PostGre SQL Mailing List <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: tablename.columnname support |
Date: | 2000-09-16 15:59:48 |
Message-ID: | 39C398F4.2CBA2566@exmachina.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
The Hermit Hacker wrote:
>
> On Sat, 16 Sep 2000, vijayendra mohan agrawal wrote:
>
> > Hi all,
> >
> > say, we have a table created by :
> > create table a ( a char(11), b char(22) );
> >
> > For adding data into table 'a', ORACLE supports column name format as
> > tablename.columnname as follows :
> > insert into a ( a.a, a.b ) values ( 'xyz', 'abc') ;
> >
> > But, PostGreSQL doesn't support... It gives parse error as follows :
> > ERROR: parser: parse error at or near "."
> >
> > Can this feature be added in PostGreSQL ???
>
> stupid question, but why would you use that format instead of doing:
>
> INSERT INTO a ( a, b ) VALUES ( 'xyz', 'abc' );
>
> Why the tablename. in front?
Just for the example:
As I do for simple web form dump to a database,
by finding the inputs related to earch table
using that prefix (sugar, doing this in Lua can
automatically create an associative array :).
- Jay
From | Date | Subject | |
---|---|---|---|
Next Message | vijayendra mohan agrawal | 2000-09-17 06:06:56 | FW: tablename.columnname support |
Previous Message | The Hermit Hacker | 2000-09-16 15:20:08 | Re: tablename.columnname support |