Squashing bugs! (July 2024)

At WhoDB, we’re always striving to make our tool more reliable and user-friendly. In that spirit, we've recently addressed several bugs that were reported by our community. Below, you'll find a summary of the most important fixes.

Bug fixes

Filter backdrop Issue

UI bugs - transparent filter selection in dark mode and Total Count: Unknown · Issue #61 · clidey/whodb

Hi me again, I found some UI bugs: In dark mode, when selecting filters, the background is transparent and it makes it hard to read In various places I see Total Count: Unknown when it comes to cou…

GitHubclidey

We had an issue with a long-standing Chrome bug where Chrome does not support nested backdrop filters. This was causing our filters to be unreadable.

SQL Where queries broke with certain table names

PostgreSQL update query breaks when table name is in a format like AdminId · Issue #60 · clidey/whodb

Hi there, I was playing around and found an issue where if I try to update a cell, it breaks with the error: keeps failing that a column doesn’t exist when it looks like it does I looked a bit thro…

GitHubclidey

Our SQL WHERE logic was incorrect in that we forgot to add quotes (") around our table names when constructing the query.

Exported graph image is of low quality

Could not capture the image · Issue #59 · clidey/whodb

Hi, using the graph function to capture image works when there are few tables (although the quality of the screenshot makes it kinda unusable) but the function stops functionning at all when using…

GitHubclidey

The exported image of the database graph becomes unreadable at certain zoom levels and when the database is massive. This should now be sorted!

Schema list was not being updated when switching between database connections

Schema dropdown list is not updated on connection profile switch · Issue #51 · clidey/whodb

In the image I tried switch to another MySQL server but noticed that the schema list shows the databases from the previous connection profile. The one I switched to has over 10 databases but we can…

GitHubclidey

One of our users was unable to see their schemas when they would switch connections. How silly of us!

The database connection profile icons had an issue displaying

feat(frontend): fix login dropdown icons for profiles · clidey/whodb@ebdffb1

A lightweight next-gen database explorer - Postgres, MySQL, SQLite, MongoDB, Redis, MariaDB & Elastic Search - feat(frontend): fix login dropdown icons for profiles · clidey/whodb@ebdffb1

GitHubclidey

We can't deprive you of your icons now can we?

Feature requests

Choose database name after connecting instead of making it part of the initial connection

Required DB names · Issue #39 · clidey/whodb

Hi, Would it be possible to NOT require a DB name when connecting to MySQL/Postgres with credentials that can access several databases and just let the user pick the one to use after connecting? Th…

GitHubclidey

One of our users pointed out that it would be very convenient to be able to select a database after connecting instead of making it part of the initial connection. This increases the flexibility as we can now connect and choose between any database that is available from that connection.

Use database credentials from the docker env configuration

[FR] Allow to configure creds/servers in docker env · Issue #32 · clidey/whodb

Hello, In the dev/ example, we have a docker compose that contain few creds to spawn some services for tests. (mysql, etc) What can be interesting is to allow to set the creds directly in docker en…

GitHubclidey

One of our users needed to configure their database connections from the docker env directly, which we think is incredibly useful to have. Thus, we updated the code to allow for that!

What's next?

These bug fixes are part of our ongoing commitment to making WhoDB the best database management tool it can be. We greatly appreciate the feedback and bug reports from our community—they help us to identify and prioritize the issues that matter most to you.

If you encounter any new issues or have suggestions for further improvements, please don't hesitate to reach out to us at support@clidey.com or by opening a GitHub issue. We’re here to help and are always looking for ways to improve.

Thank you for your continued support!