Lorefnon

The [linked pr](https://github.com/juanluispaz/ts-sql-query/pull/67) does what it was originally intended to do. However, I found that node's commonjs->esm interop also works well enough for my project. It was sufficient to just...

Interesting - I wasnt aware of the tuple comparision feature. Thanks for sharing. In my case based on the filters coming from API, I construct different joins inside the map...

So I think tuple comparisions are a great addition to this lib, and will certainly be useful. I do have some queries which I can simplify using tuple comparisions. For...

Hi, I remember this addition from the discussion in https://github.com/juanluispaz/ts-sql-query/issues/52 but I am not quite sure how this applies to context of this issue, where I was requesting simplifying union...

> If given the first query, I allow the union/unionAll to receive an array of compatible queries and all of them are unioned with the first one (the one that...

> Another idea: a type where you define the expected output that receives the TypeScript interface of each line, and that type you can use as the type for the...

@mishushakov do you have some high level thoughts on what an API would look like for this integration? Is the scope primarily crud operations ?

I don't mind g.internal. But it may not be so obvious that this works only inside an object type and nowhere else. Eg. what happens if I use `contentHash: g.internal()`...

Actually it may not be so hard to statically disallow it. Let me fiddle around and see.

Yes, basically to propagate some internal details from parent object to field resolvers.