Hmmm... that's good to know. Basically, I'm trying to model fixed order
tables in another application through a proxy mechanism (see
http://rpgsql.sourceforge.net/). I guess I will have to force row
ordering on all proxied tables.
Tim
Tom Lane wrote:
> "Timothy H. Keitt" <[EMAIL PROTECTED]
"Timothy H. Keitt" <[EMAIL PROTECTED]> writes:
> Basically, I need to update rows by offset from the beginning of the
> table.
I think you'd better rethink your data design. Tuple order in a table
is not a defined concept according to SQL. Even if we allowed queries
such as you've described, t
I see this (subselect) is available in >=7.1.
Tim
Timothy H. Keitt wrote:
> Hi,
>
> It appears that limit and offset do not work in a subselect such as:
>
> update my_table set my_col = new_val where oid = (select oid from
> my_table offset row_number limit 1);
>
> Basically, I need to
Hi,
It appears that limit and offset do not work in a subselect such as:
update my_table set my_col = new_val where oid = (select oid from
my_table offset row_number limit 1);
Basically, I need to update rows by offset from the beginning of the
table. Even nicer would be
upd
