|
|
|
Re: Generic parser API [message #526153 is a reply to message #525947] |
Fri, 09 April 2010 00:38 |
Brian Payton Messages: 154 Registered: July 2009 |
Senior Member |
|
|
OK, glad you have it working. When you say the generic parser, which
parser do you mean?
BTW, the SQLQueryParser (the LPG-based one) is designed to parse SELECT,
INSERT, UPDATE, DELETE, and MERGE statements. And the classes in the
"helper" package in org.eclipse.modelbase.sql.query plugin are designed
to get information from a generated query model such as all the column
references in a statement.
Slavik Taubkin wrote:
> Thank you for the reply!
> I have to analyse different kinds of statements (including DELETEs,
> UPDATEs, INSERTs). I "solved" this problem by splitting the original
> statement into smaller pieces that can be parsed with the generic parser.
>
> Regards,
> Slavik
|
|
|
|
Re: Generic parser API [message #597416 is a reply to message #525947] |
Fri, 09 April 2010 00:38 |
Brian Payton Messages: 154 Registered: July 2009 |
Senior Member |
|
|
OK, glad you have it working. When you say the generic parser, which
parser do you mean?
BTW, the SQLQueryParser (the LPG-based one) is designed to parse SELECT,
INSERT, UPDATE, DELETE, and MERGE statements. And the classes in the
"helper" package in org.eclipse.modelbase.sql.query plugin are designed
to get information from a generated query model such as all the column
references in a statement.
Slavik Taubkin wrote:
> Thank you for the reply!
> I have to analyse different kinds of statements (including DELETEs,
> UPDATEs, INSERTs). I "solved" this problem by splitting the original
> statement into smaller pieces that can be parsed with the generic parser.
>
> Regards,
> Slavik
|
|
|
Powered by
FUDForum. Page generated in 0.02539 seconds