Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Connecting from query tools failed due to difference problems #340

Closed
huynguyn2000 opened this issue Jan 2, 2025 · 3 comments
Closed

Connecting from query tools failed due to difference problems #340

huynguyn2000 opened this issue Jan 2, 2025 · 3 comments
Assignees
@VWagen1989
Labels
bug Something isn't working compatibility Be compatible with some old fashion request

Comments

@huynguyn2000
Copy link

huynguyn2000 commented Jan 2, 2025 •
edited
Loading

I had set up MyDuck Server in Server Mode, I want to connect it through some query tools like Metabase, DBeaver, PgAdmin, Navicat, but all of them are also not work. I meet difference problems when connecting via those tools.

With DBeaver the connection error is: Catalog Error: Type with name regclass does not exist!
PgAdmin: Unable to connect to server: fallback statement execution failed: Catalog Error: Scalar Function with name set_config does not exist!
Navicat: fallback statement execution failed: Error: Values list "d" does not have a column named "dattatablespace"
Metabase: connections could not be acquired from the underlying database! ( connecting to metabase is necessary, if it coundn't happen, I have to stop using MyDuck Server )

I'm wondering if MyDuck Server is using the standard Postgres protocol, because it's fine to use those tools to connect to other PostgreSQL databases, these problems only occur when I connect to MyDuck Server.

Any answers are appreciated !!
@VWagen1989
Copy link
Contributor

@huynguyn2000 Hi, Thanks for this detailed feedback for MyDuck server!

Yeah, it seems there still be some compatibility problems between MyDuck server and the PostgreSQL wire protocol. We'll take an action to address this issue now. Please stay tuned!

@VWagen1989 VWagen1989 added compatibility Be compatible with some old fashion request Discord bug Something isn't working and removed Discord labels Jan 2, 2025
This was referenced Jan 2, 2025
Closed
Merged
VWagen1989 added a commit that referenced this issue Jan 9, 2025
@VWagen1989
fix: resolve compatibilities for Metabase (#340) (#352)
34b0213 
* fix: solve issue of handling extended query (#342)

* fix: add internal view pg_stat_user_tables and add query rewritten for type casting

* create internal macros to mimic some pg system functions

* wip: add pg_catalog.pg_get_indexdef

* fix: use a better regex pattern to replace the sys function names

* fix: make 'SET SESSION CHARACTERISTICS TRANSACTION ...' work and use session level pgtypes.Map for each session to encode results

* fix: cast DuckDB HUGEINT to pgtype.Numeric

* fix: adopt CR feedbacks

* fix: add tests and resolve failed tests
@VWagen1989 VWagen1989 self-assigned this Jan 9, 2025
@VWagen1989
Copy link
Contributor

@huynguyn2000 Metabase is supported on MyDuck Server in #352, please have a try!

@huynguyn2000
Copy link
Author

@VWagen1989 Thanks for your support, I will take a look tmr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VWagen1989 VWagen1989

Labels
bug Something isn't working compatibility Be compatible with some old fashion request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@huynguyn2000 @VWagen1989