limads/queries

Queries is a workbench to interact with relational databases, with initial support for Postgres.

queries's Issues

SSL Doesn't Work with AWS

Hello!

First, I love this app. I've been waiting a long time for a gtk4 sql client, and I'm happy to see you're working on this. Thank you!

I can't connect to my remote postgres instance. It's hosted on an AWS server, and so the hostname doesn't match what I put in the configuration fields. Looks like you're using sslmode=verify-full, which simply won't allow this connection. If you allow us to use verify-ca instead then it will work if I provide the pem file for AWS.

Error from psql:

psql: error: connection to server at "" (), port 5432 failed: server certificate for "" does not match host name ""

Error from Queries:

Error performing TLS handshake: error: 0A0000SSL routines:tls_post_process_server_certificate:certificate verify failed:../ssl/statem/statem/clnt.c:1887:: hostname...

The error times out after like three seconds so I had to do a bunch of takes to get that right. Hope there are no typos.

Thanks! I'm excited to start using this.

thread 'main' panicked at 'assertion failed: `(left == right)`

When choosing to save an Untitled script by pressing Ctrl + S, but then choosing not to save by pressing Esc, and ultimately choosing to store the script with Ctrl + S, a reproducible crash occurs in v1.5.0:

thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `true`,
 right: `false`', /run/build/Queries/deps/gtk4/src/auto/file_chooser.rs:323:13
stack backtrace:
   0:     0x55b177549980 - <unknown>
   1:     0x55b17756daae - <unknown>
   2:     0x55b177544f55 - <unknown>
   3:     0x55b17754b1b3 - <unknown>
   4:     0x55b17754ae9f - <unknown>
   5:     0x55b17754b85a - <unknown>
   6:     0x55b17754b757 - <unknown>
   7:     0x55b177549e2c - <unknown>
   8:     0x55b17754b472 - <unknown>
   9:     0x55b177152d93 - <unknown>
  10:     0x55b17756b4cb - <unknown>
  11:     0x55b1771441eb - <unknown>
  12:     0x55b17731e92f - <unknown>
  13:     0x55b1774fe424 - <unknown>
  14:     0x55b1774f5875 - <unknown>
  15:     0x7f473772e681 - g_main_context_dispatch
  16:     0x7f473772ebd8 - <unknown>
  17:     0x7f473772ec73 - g_main_context_iteration
  18:     0x7f4737971bad - g_application_run
  19:     0x55b177158d25 - <unknown>
  20:     0x55b17715b347 - <unknown>
  21:     0x55b1771541a3 - <unknown>
  22:     0x55b1771541b9 - <unknown>
  23:     0x55b177540a3f - <unknown>
  24:     0x55b17715bc38 - <unknown>
  25:     0x7f473722954a - <unknown>
  26:     0x7f473722960b - __libc_start_main
  27:     0x55b1771530c5 - <unknown>
  28:                0x0 - <unknown>

Unable to parse (uuid)

For now, Queries is not able to display Postgres' UUID columns:

AUR Package release

First of all thank you for this project.
I wanted to inquire if a possible AUR package is in planning?

update building documentation

The build process is broken right now.

Doing a cargo build doesn't work. It requires to have papyri, stateful, stateful-derive cloned in directories next to queries.
Since stateful-derive is not publicly available as one of your repositories, I'm at a dead-end.

Certain UI elements not respecting dark mode

As shown below
(Loving the app though, great stuff 😃)

[Feature Request] MySQL/MariaDB support?

App shown as "Stopped Recieving Updates" in Gnome Software 45.

This might be an error on flathub's part, as it only effects the flatpak version.

Gnome introduced a feature to flag flatpak applications that are not being actively maintained to prevent security issues and bad ux from outdated software.

Support .sqlite files

Just as the title suggests, i have found that it is unable to open .sqlite files, which is a shame, as it looks like a well designed interface for DB editing.

Overly restrictive connection settings

As much as I appreciate the restrictions in connecting to localhost databases, I had some difficulties in finding the correct combination of allowed settings. For the localhost alias may translate to an IPv4 or IPv6 address, depending on the availability of network addresses in the local nss, and could also very well be something different other than 127.0.0.1 or localhost.

For example, the valid loopback address 127.0.10.10 is not recognised as part of the loopback interface, as defined in RFC 6890, and will require a secured connection to the database.

For IPv6, also the networks ::1/128 and fe80::/10 should be considered link-local addresses.