Rene Saarsoo

> But the right to determine whether the syntax is correct is in your hands, isn't it? Correct. I also maintain the [parser](https://github.com/nene/sql-parser-cst). Regarding the specific error. It would be...

Yes, that's the downside of this architecture. That's why the support of MariaDB is also labeled ["Experimental! expect crashes"](https://github.com/nene/prettier-plugin-sql-cst?tab=readme-ov-file#choosing-an-sql-dialect). There are other SQL formatting tools out there which don't have...

Also, there is now `sqlAcceptUnsupportedGrammar` option which resolves this whole issue. Though it should be used with caution, as it will just silently skip any unrecognized SQL. Better to only...

Indeed. You're right. That option works fine when the type of statement itself isn't recognized (like when you would attempt to parse `CREATE OPERATOR ...` which isn't supported at all),...

Interesting... because according to [MySQL documentation for CREATE TABLE](https://dev.mysql.com/doc/refman/9.1/en/create-table.html), there is no such syntax. The docs say that one can only use the `ON UPDATE` as part of `REFERENCES` clause....

Thanks for reporting. - The second problem can be dealt with the help of `paramTypes` configuration. [See the FAQ](https://github.com/sql-formatter-org/sql-formatter?tab=readme-ov-file#my-sql-contains-templating-syntax-which-sql-formatter-fails-to-parse). - The first problem is a case of Spark SQL syntax...

Yeah, this `${...}` syntax is actually supported by default. However the formatter assumes that `${...}` constitutes some kind of identifier. If it works as just a plain string substitution, then...

Additionally the same issue happens with `TABLE` type, used when creating table functions. For example in: ```sql create table function foo () returns TABLE as select 'John' as fname, 64...

Looks like this is actually a problem with BabylonJS itself. I created a scene with plain babylonJS on another canvas alongside the react-babylonjs scene. It kind of works, I guess,...

I tried the following, but the exact same problem happens (the two gizmos appear in the second canvas): ```jsx export function Area3D() { const meshRef = useRef(null); const gizmoRef =...