Tobias
Tobias
Huh. That's an old one. I am still no fan of it: https://medium.com/codex/effective-java-implement-serializable-with-great-caution-df123eb51cdf
see #479 as well
You are right. There are a lot of issues for alter table. There is much room for improvements. Pull requests are welcome. Please only one commit and pull request per...
Copy ist not supported by JSqlParser.
This is not yet planned. Will you provide a pull request?
That is right. JSqlParser does not support this old join syntax in this between construct.
Don't you mixing up here SQL and Velocity template constructs? Sorry for asking.
The best way to tackle this, would be to accept three S_CHAR_LITERALs. #result('field' 'type' 'alias') would be "(" S_CHAR_LITERAL S_CHAR_LITERAL S_CHAR_LITERAL ")" I see no problem here. I do not...
Nevertheless I would prefer the preprocess way, to not struggle with JSqlParser updates. I would replace all constructs to a parsable identifier form. Maybe #result('field' 'type' 'alias') to __result___field____type____alias___
So far I agree. Tagging or marking seems less invasive. I also recognized that in those packages are classes, that are not fitting your improvement suggestion: e.g. ExpressionList, MultiExpressionList, .......