What is the equivalent of the following in ElevateDb

Update table1
set table1.field1=table2.fieldx
from table1
on table1.fieldy=table2.fieldz
where <condition>

Hendrik,

<< What is the equivalent of the following in ElevateDb

Update table1
set table1.field1=table2.fieldx
from table1
on table1.fieldy=table2.fieldz
where <condition> >>

See here:

http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=19&msg=1020&page=1#msg1020

Although I must point out that we may re-introduce the joins at some point.
However, I don't have any firm dates for that at this time.

--
Tim Young
Elevate Software
www.elevatesoft.com

I would strongly support re-introduction of the join as the performance hit
for multi-column update with sub-selects is huge!
For example, updating payroll master where you have 30-40 fields or
financial GL or PayPeriod Distributions where again
you have 13 and/or 27 fields.  The previous syntax gives us excellent
response and we need that advantage.

Donat Hebert


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:1AF22D31-24CF-4FC8-A461-DD1D49898C0B@news.elevatesoft.com...
> Hendrik,
>
> << What is the equivalent of the following in ElevateDb
>
> Update table1
> set table1.field1=table2.fieldx
> from table1
> on table1.fieldy=table2.fieldz
> where <condition> >>
>
> See here:
>
> http://www.elevatesoft.com/scripts/newsgrp.dll?action=openmsg&group=19&msg=1020&page=1#msg1020
>
> Although I must point out that we may re-introduce the joins at some
> point. However, I don't have any firm dates for that at this time.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Donat,

<< I would strongly support re-introduction of the join as the performance
hit for multi-column update with sub-selects is huge! For example, updating
payroll master where you have 30-40 fields or financial GL or PayPeriod
Distributions where again you have 13 and/or 27 fields.  The previous syntax
gives us excellent response and we need that advantage. >>

You'll have to use multiple steps and/or SQL statements for now.  I would
suggest coding a stored procedure to do what you want using a driver cursor
for updating the related rows as necessary.

--
Tim Young
Elevate Software
www.elevatesoft.com