clidey / whodb

A lightweight next-gen data explorer - Postgres, MySQL, SQLite, MongoDB, Redis, MariaDB & Elastic Search with Chat interface
https://whodb.clidey.com
GNU General Public License v3.0
1.9k stars 56 forks source link

Unable to use sqlite #199

Closed ocrumbs closed 3 weeks ago

ocrumbs commented 1 month ago

Hi,

Thanks for the project, I built this locally and run the binary directly without docker, to be able to use it with sqlite. However, I am getting this error.

Screenshot from 2024-10-05 16-25-01

Thanks again!

hkdeman commented 1 month ago

Hey! There is a small bug you found here - when running locally - it actually checks for a tmp folder inside the core folder (our backend). If you put your sqlite3 database there - you should be able to find it in this dropdown.

I would recommend using docker/docker-compose - the experience is significantly better and plus you can easily mount the file to /db/ without altering/linking the folder in which it is being used.

We will definitely add this to our docs and fix the bug of showing on the UI as it is super confusing right now!

ocrumbs commented 1 month ago

Thanks for the quick response, I now have tmp folder in place but still facing the same issue. Do you think the issue may be related to the unauthorized graphql response from the server (among other things) preventing from moving further?

I cannot use docker because I will need to eventually run on a machine with no docker installation :unamused:

Thanks !

hkdeman commented 1 month ago

That's unusual. Let me check this out and get back on this thread.

wbste commented 1 month ago

Yeah, same issue here. Tried both the volume mount method and the profiles method. I thought if I set ENVIRONMENT in the compose file to anything but dev it would work, but obviously not... (yes my db name matched the below for testing)

services:
  whodb:
    image: clidey/whodb
    ports:
      - "8080:8080"
    environment:
      WHODB_SQLITE3_1: '{"database":"sample.db"}'

Any chance we could do like a file picker for sqlite files instead?

Or maybe allow mapping an entire directory so we can just add in them at will, like below in a db folder?

docker run -it -v ./db:/db/ -p 8080:8080 clidey/whodb:latest

hkdeman commented 3 weeks ago

Thank you so much for waiting! We have realized this bug was caused due to change in the schema. We have resolved this and will be releasing next! https://github.com/clidey/whodb/pull/224

wbste commented 3 weeks ago

Nice! Got it working now! I can add whatever sqlite files i want to the db folder and restart the container and it works! Thanks!

  whodb:
    image: clidey/whodb
    volumes:
      - ./db:/db
  ...
hkdeman commented 3 weeks ago

This is great! Glad it works now. Would love any feedback, suggestions, and use cases that we can improve on.

ocrumbs commented 3 weeks ago

:pray: :pray:

Thanks a ton, works very well now .