guptamanan100

Right exactly!

I wrote it, but of course I used AI to polish it :smile: It would actually be ironic if I didn't use Claude to write about how Claude accelerated my engineering!

Good question! The main reason is that sqlglot is written in Python, so it wouldn't integrate natively with our Go codebase. We actually faced a similar decision with pg_query_go (https://github.com/pganalyze/pg_query_go) and passed on that too, anything that requires bridging another language means translating the AST back into Go, which adds a performance cost we wanted to avoid.

Hey HN, I'm the author. Happy to answer questions or discuss further.

Oh, I see, that's unfortunate! Hopefully, we can remedy that though as soon as possible.

Thank you for the compliment!

We recently started adding support for CTEs in Vitess! You can check out https://github.com/vitessio/vitess/pull/14321 if you want to see some technical details of the implementation.

For now, we have added preliminary support by converting them to derived tables internally, but we believe that we need to make CTEs first-class citizens themselves of query planning, specifically because recursive CTEs are very hard to model as derived tables. Once we make that change, we can look towards supporting recursive CTEs.

This however will take some time, but then, all good things do!

Yep! Aaron is great, isn't he!!? I make it a point to watch all the videos he puts out. We appreciate your support!

I am the other post-author, and I am available too.