Will Dean

I can take a look at this. Seems to only be in [one location](https://github.com/aesara-devs/aesara/blob/c8908e5a27ae34d16bc3c025424a77ac0268ac51/aesara/graph/basic.py#L513) at first glance. Are there any of the initializations in [type module](https://github.com/aesara-devs/aesara/blob/c8908e5a27ae34d16bc3c025424a77ac0268ac51/aesara/tensor/type.py) that act differently? Appears...

I believe using the dialect specific Query class is the recommended way of using. That's somewhere in the README I am not sure if passing dialect kwarg is recommended. Definitely...

Can you try without the () The from_ is a classmethod rather than a method

Doesn't seem ideal. Would you like to make a PR and write some tests against this behavior?

Seems like that is something wrong with chromadb rather than pypika as it is happening in their codebase. Have you raised an issue with that project?

Check out this example in the tutorial it, it is very similar: https://pypika.readthedocs.io/en/latest/2_tutorial.html#with-clause Does this fit your use case? ```python from pypika import Table, AliasedQuery, Query efg = Table('efg') sub_query...

Seems like the tests that ran were good. Is there an issue with the coveralls version @AzisK ?

Out of my wheelhouse, sorry. @AzisK will have to take care of it

> @AzisK @wd60622 woohoo it's passing! Can it be merged? Looks good. Need @AzisK to do the merge 😅

I think this sounds very useful. Do you think returning Table objects and Field objects instead of string would still be useful?