Is SQL Anywhere trying to be too helpful? -- issue 2

[David]

The following appears to be working as designed however should the
design provide an option to disable this assistance when it is not desired?

Is there a switch or should there be a switch to prevent the add foreign
key command from adding columns to child tables when they do not exist
in the currently defined table? Again this could be a vendor provided
optional switch (settable by the user for the database to provide
creation time errors - add foreign key) to preventing system generated
problems (generally found at execution time) for users that commit as
part of their standards to defining the necessary column(s) in the child
table in advance.

This is yet another of those system trying to be nice (helpful) features
that cause more problems in my opinion than they are worth. (kinda like
the multiple interpretations of a click (select word, sentence,
paragraph -- too subtle to be useful and often an annoyance instead of a
help)

[Breck Carter [TeamSybase]]

I agree... this is an obscenity that should be removed from SQL
Anywhere. Under no circumstances should it default to adding a mystery
column to a table.

Breck

--
Breck Carter http://sqlanywhere.blogspot.com/

RisingRoad SQL Anywhere and MobiLink Professional Services
breck....@risingroad.com

[Volker Barth]

Seconded!
(Particularly as it is quite difficult to even notice that something
went wrong).

Volker

Breck Carter [TeamSybase] schrieb: