Related articles |
---|
Backward semantic analysis of Oracle SQL yong321@yahoo.com (2000-08-10) |
Re: Backward semantic analysis of Oracle SQL Frank.Gerlach@brokat.de (Frank Gerlach) (2000-08-13) |
Re: Backward semantic analysis of Oracle SQL bonzini@gnu.org (2000-08-13) |
From: | Frank Gerlach <Frank.Gerlach@brokat.de> |
Newsgroups: | comp.compilers |
Date: | 13 Aug 2000 19:02:44 -0400 |
Organization: | Brokat AG |
References: | 00-08-052 |
Keywords: | design |
I guess this is due to the separation of parser and scanner. The
"selec" error is most probably detected by the scanner and immediately
reported. The set of tables of your select stmt might be stored in
reverse order by the parser (as the order is of no relevance and this
allows for a simple stack data structure) and then checked for
existence.
yong321@yahoo.com wrote:
> I hope this is not off-topic. The Oracle database SQL interpreter
> seems to do semantic analysis from the end of a SQL statement to the
> beginning. I wonder why they do this and whether there's anything bad
> about it.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.