Open jubinmytheen opened 1 year ago
Hey - thanks for reporting this. This is a bug with our result formatting, which can be hit in some cases when we attempt to build a resultset with types that are not natively supported in ReadySet's dataflow graph. Generally, we still support proxying these types to your upstream database.
In the meantime, you can work around this bug by setting the DBeaver preferQueryMode
option to simple
. This will rely on Postgres' Simple Query protocol.
We'll keep you updated with progress for this fix.
Hi @jubinmytheen, this should be fixed in the September monthly release a few weeks from now, now that #266 and #268 are both done. Once the September release is out and you've upgraded to it, the workaround that @dfwilbanks395 posted should no longer be needed. At that point, if you can confirm this is no longer a problem for you, feel free to close this issue; otherwise, let me know if the problem persists and we can take a closer look.
We have configured ReadySet through Docker and we can connect the ReadySet application through psql command. But when we try to access through DBeaver, we are getting the below error.
Is there anything we need to configure on ReadySet to connect through DBeaver?