parse is responsible for parsing a
native query string and recognizing tokens defining named of ordinal
parameters and providing callbacks about each recognition.
| Modifier and Type | Field and Description |
|---|---|
| private static final String | |
| private static final BitSet |
| Access | Constructor and Description |
|---|---|
| private |
| Modifier and Type | Method and Description |
|---|---|
| private static void | |
| public static void | parse(String
The string to be parsed/tokenized. sqlString, ParameterRecognizer The thing which handles recognition events. recognizer, boolean Whether to ignore ordinal parameters in native queries or not. nativeJdbcParametersIgnored)Performs the actual parsing and tokenizing of the query string making appropriate callbacks to the given recognizer upon recognition of the various tokens. |
| public static void |
| HQL_SEPARATORS | back to summary |
|---|---|
| private static final String HQL_SEPARATORS | |
| HQL_SEPARATORS_BITSET | back to summary |
|---|---|
| private static final BitSet HQL_SEPARATORS_BITSET | |
| ParameterParser | back to summary |
|---|---|
| private ParameterParser() Direct instantiation of ParameterParser disallowed. | |
| checkIsNotAFunctionCall | back to summary |
|---|---|
| private static void checkIsNotAFunctionCall(String sqlString) | |
| parse | back to summary |
|---|---|
| public static void parse(String sqlString, ParameterRecognizer recognizer, boolean nativeJdbcParametersIgnored) throws QueryException Performs the actual parsing and tokenizing of the query string making appropriate callbacks to the given recognizer upon recognition of the various tokens. Note that currently, this only knows how to deal with a single output parameter (for callable statements). If we later add support for multiple output params, this, obviously, needs to change.
| |
| parse | back to summary |
|---|---|
| public static void parse(String sqlString, ParameterRecognizer recognizer) throws QueryException | |