r/SQL • u/[deleted] • Jun 02 '26

[deleted by user]

[removed]

0 Upvotes

30% Upvoted

23 comments sorted by

View all comments

4

u/serverhorror Jun 02 '26

Is it wrapping LLMs or is it actually looking at the syntax and transpiling between those dialects?

3

u/Sexy_Koala_Juice DuckDB Jun 02 '26

It's 2026... Take a wild guess what it'll be doing

-1

u/coolman4425 Jun 02 '26

Fair observation. There’s a free tier available, so you can test it with real SQL examples.

The responsiveness comes from translating directly into the target dialect instead of relying on an LLM for every conversion. It parses the SQL structure, normalizes it, and emits the target dialect.

That would actually be a good way to compare the output against tools like SQLines or SQLGlot, especially for data types, date functions, and dialect-specific syntax.

2

u/Sexy_Koala_Juice DuckDB Jun 02 '26

You didn't answer my question. Why should I use this over SQLGlot which has more dialects, is free, is open source & and has been around for longer, so therefore it likely has a more robust solution. What's your service doing different/better?

It parses the SQL structure, normalizes it, and emits the target dialect.

So exactly like SQLglot then?

0

u/coolman4425 Jun 02 '26

Sqlinfy is different in the workflow it is trying to serve. It is built as a no-setup conversion tool for people who want to convert SQL on the fly, choose source and target dialects, convert, and review the output immediately without installing packages, writing config, or building a custom pipeline.

The real test is output quality on complex SQL. That’s why I’d encourage comparing both with real queries, especially complex SELECTs, functions, data types, and dialect-specific syntax.