I recently downloaded and installed ASA9 EBF1250 and discovered that using
'order 0' in create trigger now causes a syntax error. No previous version
(5, 6, 7, 8, 9 prior to 1250) of ASA I have used has behaved this way. Is
this a bug, or an intentional behaviour change? If it's the latter plenty of
Powerdesigner-generated triggers (like mine) will be broken.

Dave.

Can you please post an example?

Thanks

Glenn

Dave Foulkes wrote:
--
Glenn Paulley
Research and Development Manager, Query Processing
iAnywhere Solutions Engineering

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports: http://casexpress.sybase.com/cx/cx.stm

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer

From the Powerdesigner 'crebas.sql' script:-


create table "BPWPLAN"."ATTRIBUTE"
(
"ATTRIBUTE_HANDLE" integer not null
default autoincrement,
"ATTRIBUTE_ID" char(8) not null,
"ATTRIBUTE_NAME" char(24) ,
"ATTTYPE_HANDLE" integer not null,
primary key ("ATTRIBUTE_HANDLE"),
unique ("ATTTYPE_HANDLE", "ATTRIBUTE_ID")
);

And from the Powerdesigner 'cretrg.sql' script:-

create trigger "tub_attribute" before update of "ATTRIBUTE_HANDLE",
"ATTRIBUTE_ID",
"ATTTYPE_HANDLE"
order 0 on "BPWPLAN"."ATTRIBUTE"
referencing new as new_upd old as old_upd for each row
begin

if ((new_upd."ATTTYPE_HANDLE" is null and old_upd."ATTTYPE_HANDLE" is
not null) or
new_upd."ATTTYPE_HANDLE" <> old_upd."ATTTYPE_HANDLE" ) then
call bpwPutError('"tub_attribute"',
'BPW_SQL_ERR_CANNOT_CHANGE_PARENT', '"ATTRIBUTE"."ATTTYPE_HANDLE"',
old_upd."ATTTYPE_HANDLE", new_upd."ATTTYPE_HANDLE");
end if;
end;

If I replace 'order 0' with 'order 1' all is happy.

Dave.


"Glenn Paulley" <paulley (AT) ianywhere (DOT) com> wrote

This problem will be fixed in build 1253. Sorry for the inconvenience and
thanks for letting us know. As a temporary workaround, you can remove the
ORDER 0 from the statement.

Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
Developer Community at http://www.ianywhere.com/developer

"Dave Foulkes" <dave.foulkes (AT) NOSPAM (DOT) dial.pipex.com> wrote

I'm just relieved to hear that it was an unintentional slip, and that ORDER
0 will be working again soon.

Thank you for your speedy response.

Dave.

"Bruce Hay" <hay at sybase dot com> wrote