| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
flex does not(*) support UTF-8, therefore
alpha [a-z_\.À-ﾟ]
has always been interpreted by flex as
alpha [a-z_\.\xC3\x80-\xEF\xBE\x9F]
I assume this is not what was indetend and the only reason it worked, is because C3 (195),BE (190) and 9F (159) are already covered by 80-EF (128-239). Incidentally this range would also cover the whole Unicode BMP in UTF8.
This change should make it more obvious.
(*) There were some patches in 2012 and 2014 but they don't seem to have been merged.
|
| |
|
|
| |
cause visible changes)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
- Tweak README
|
| | |
|
| |
|
|
|
|
|
|
| |
by using the lexer SPTokenizer
- the new method is called splitStringIntoRangesOfSQLQueries: in SPSQLParser
- in CustomQuery's method queryAtPosition: can be found a test case which is as default not activated
- must be improved further
|
| | |
|
| | |
|
|
|
- this is an approach to make usage of lex to split a string very fast into SQL queries considering the "delimiter" switch and compound-statements via CREATE ... BEGIN ... END; without using "delimiter"
|
