variable vs colname - should not compiler give a warning?

Hi,

table A has column B.  There is also variable B in 4gl program.

Then sql statement eg like

delete from A where B="X"
(meaning: delete from A where A.B="X")

may lead to unexpected results when author (me!) is not aware of priority
of "variable" parsing - compiler seems to look first at variable
definitions and than up to table colnames. I really would expect the
inverse "logic". Is this common behavior in 4gls? I've spent a nice hour by
WTF?!....

Thanks, Michal



------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d