Andrew Valleteau

> Can this be reopened. Im still facing this issue and looking at the changelog this was reverted. Yes it has been reverted as it caused unexpected regressions with previous...

> @avallete - Are you guys fixing this still? Everything was working fine before you reverted it... Hey ! Thanks for the feedback and yes we are. We think that...

@jdgamble555 Happy to tell you that we just released [v2.47.8](https://github.com/supabase/supabase-js/releases/tag/v2.47.8) that include the typing inference rework which should fix the inconsistents typing on joined fields.

@brianc I did my best but had to forge a specific invalid packet to force the parse error (since we can't reproduce the "max array error" in JS really). I...

Hey there ! We've reworked the result inference in `postgrest-js` to address the typing issues mentioned above. The changes are available in a canary release, and we're actively seeking your...

The fix has been released in `supabase-js` v2.46.0. I'm closing this issue, but feel free to reopen if you encounter any further errors.

I've tried to poke a bit with it. And while implementing things at the "connection" level for each message might help mitigate those issues. I think there is still one...

Hey @brianc ! Thank's for the comment. Indeed, as stated in the issue, the use case here is actually one where the actor "performing the query" and the "database" are...

Hi @chesterhow, Thanks for bringing this up! It’s definitely an interesting idea, but I don’t see us implementing this anytime soon. Here’s why: Implementing this would mean we’d need to...

Hey @chesterhow ! Indeed using `.overrideTypes` or an explicit cast are two valid ways to deal with this depending on your preferences.