Differences between revisions 1 and 2
Revision 1 as of 2005-11-29 21:28:53
Size: 727
Editor: DanDebrunner
Comment:
Revision 2 as of 2009-09-20 22:11:31
Size: 729
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
Currently the nodes are created indirectly through a !NodeFactory, however [http://issues.apache.org/jira/browse/DERBY-673 DERBY-673] describes removing the factory. Currently the nodes are created indirectly through a !NodeFactory, however [[http://issues.apache.org/jira/browse/DERBY-673|DERBY-673]] describes removing the factory.

Derby SQL Parsing

The input to the parser is a Java string containing the text of the SQL statement. Since the statement is a Java String its character set is always Unicode.

The parser is generated by javacc and its source is in the file  /trunk/java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj 

Parsing creates a tree of query nodes, each represented by an instance of a sub-class of org.apache.derby.impl.sql.compile.QueryTreeNode class. Each node represents a database operation.

Currently the nodes are created indirectly through a NodeFactory, however DERBY-673 describes removing the factory.

Onto the bind phase: LanguageBind

LanguageParse (last edited 2009-09-20 22:11:31 by localhost)