CONVERT() - data type is wrongfully parsed as a column #644

Activity

1. wumpz commented on Jul 15, 2018

   

   wumpz

   on Jul 15, 2018

   Member

   More actions

   I would say it's by design. Jsqlparser is only a parser and cannot differ between column, identifier, typename, ... Why not leave it like it is and do the semantics later. Maybe we should rename Column to DBidentifier.
2. wumpz commented on Jul 15, 2018

   

   wumpz

   on Jul 15, 2018

   Member

   More actions

   It is the special definition of the convert function that could be very different on other dB systems.
3. wheredevel commented on Jul 16, 2018

   

   wheredevel

   on Jul 16, 2018

   Last edited by wheredevel

   Author

   More actions

   Well, if we had a way to indicate the dialect the parser ahead - that would solve it.
   For now, we just need it to parse this MSSQL dialect properly. (MySQL's is similar.)
   So, we implemented this.
4. manticore-projects

   closed this as completedin #1778on Jun 1, 2023