Hello,
While I can't answer my question, I am afraid I did not understand your
intentions either. The update you mentioned may not return consistent
results, isn't it? You are not ordering the data in any particular manner
and there is no unique column either. So the result of the update will
d
Hello.
First,we can not execute the SQL which Paulo indicated in PostgreSQL.
See this manual.
==
http://www.postgresql.org/docs/8.4/interactive/sql-update.html
Compatibility
This command conforms to the SQL standard, except
create table test(i number , j number);
insert into test values(1,2)
insert into test values(1,3)
insert into test values(1,4)
select * from test;
I J
-- --
1 2
1 3
1 4
My intentions:
after update
select *
Howdy,
I'm trying to create a schema in which there will be simple a view for
each table that will have the same columns and can be acted on in the
same way as the underlying table
An example of one table and its view would be:
CREATE TABLE test (id int, text_field varchar(100));
CREATE VIEW _te
On Thu, 6 Nov 2003 00:50:06 +0900, Michael Glaesemann
<[EMAIL PROTECTED]> wrote:
>>> What I came up with was deleting and reinserting the relevant
>>> ordercharges rows
>>
>> This might have unwanted side effects (think ON DELETE CASCADE).
>
>Good point. At this stage in my PostgreSQL progress, I h
Manfred,
Thanks for taking the time to walk me through this. You've pointed out
things I've noticed when writing queries and wondered about. (More
specific comments—and commentary—below.
What I came up with was deleting and reinserting the relevant
ordercharges rows
This might have unwanted sid
On Wed, 5 Nov 2003 02:58:28 +0900, Michael Glaesemann
<[EMAIL PROTECTED]> wrote:
>> UPDATE ordercharges
>>SET orderchargeasbilled = 0.065 * sale.orderchargeasbilled
>> FROM orders AS o, ordercharges AS sale
>> WHERE ordercharges.orderchargecode = 'S&H'
>>AND ordercharges.orderid = o.orde
