Hi @Stefano Gallotta
Glad you got something to work; but I am a little confused about something:
In my experience the SQL statements are executed from the SQL client; not d3 itself. The OBDC interface exposes and performs translates in real time etc for the tables which are now inside the SQL client; so any syntax issues are the domain of the SQL client. Your comment suggests to me you think the syntax issue is with d3/Rocket?
Which client one are you using? For example, are you using MS Access? MS SQL server? MS SQL-server lite [or whatever it is called, I forget!]
Or are you writing a routine outside of d3 but never-the-less in "SQL-land" via a library perhaps in c#; etc? In which case, once again the SQL syntax is dependent on that library or version; not d3.
I realise that the ODBC interface itself does not support the full set of SQL syntax; but I always took that to mean there was no equivalent within the ODBC driver; not that it affected legal SQL syntax. But maybe I'm wrong?
My experience with SQL via the ODBC connector is limited with all examples I've done are from SQL client products like Access, MS SQL.