> >Actually, I disagree. IMO, it should raise an error so that it shows
> >the user that there is a field "F2" in the table. That way, "undefined"
> >behaviour can be avoided.
> >
> >
> >
> Martijn, if I thought everyone would agree, I wouldn't have raised it
> for discussion.

;-)

> Maybe would should play a game. We'll call anyone who favors
> "undefined" type A; anyone who favors a rule type B, and anyone who
> favors an error, type C. I've come out of a type A. You're clearly a
> type C. Can we guess were everyone else will fall?
>
> Helen, I'd guess B. Paul, loosy-goosy, definitely an A. Dmitri likes
> order, so I'll guess B. Like always, I haven't the slightest idea of
> where Nickolay might land, but we can probably rule out A.
>
> Other guesses?

Well, the reason I'm type "C" is that I look at it from a user
point of view. I remember someone saying "give a user enough
rope and they will hang themselves". In this particular case, I'd
like to avoid users entangling themselves.

Remember the ambiguity issue? Those results were "undefined"
and it was fixed.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com