Phillip Cloud
Phillip Cloud
@icexelloss Thanks for chiming in! There are a few reasons why we're undertaking this change. We want to tackle big ticket items all of which are made unreasonably difficult by...
> I feel like there is a reason that Node/Expr are structured this way in the first place and concerned about that fitting with matchpy shadows the reason/benefit that Node/Expr...
> @cpcloud this is a really aggressive change and will likey blow up the world. Can you explain the rationale See all the text above. Happy to answer any specific...
It'll be a bit before we merge it. Are there any specific questions I can answer?
Hi @webmiche 👋🏻! This is most definitely a work in progress. We'd happily accept a PR that implements the rules on the page you link to if you're up for...
Sounds great! Looking forward to the PR.
@kszucs I'm going to move this off the 3.0.0 milestone.
There might be an easy win for a subset of use cases here. @prmoore77 What if `.sql` could automatically convert the SQL string to the appropriate backend dialect? This is...
@prmoore77 Does #4335 cover you desired use case? If so, would you mind closing out this issue and we can continue the discussion there?
@ams1 Yeah! We've been thinking about using [`sqlglot`](https://github.com/tobymao/sqlglot) for this, since we're already using it and it's a full featured no-dependency SQL parser for Python.