Dennizz

Hey HN, creator of DB Pilot here.

I first announced DB Pilot on HN back in April: https://news.ycombinator.com/item?id=35761979.

Since then a lot has improved: More databases are supported, most of the product can now be used for free, and most importantly:

The app now comes with an analytics workspace powered by an embedded ClickHouse instance, running locally on your machine. This allows you to query local files, files on S3, PostgreSQL, SQLite & more - and all of those at once.

Embedding ClickHouse was possible thanks to chDB (https://github.com/chdb-io/chdb). A recent discussion on HN about it: https://news.ycombinator.com/item?id=37985005

If you mean the common OpenAI API key, I'm not sure how that's different in regards to feeling secure compared to separate keys. Would you mind elaborating further, please?

To clarify, the common API key is known only by my server, not by the app!

Not yet but I have it in my list of TODOs!

I just pushed a new release. It should work now!

To install the new version, just restart the app. It should then prompt you to install the update.

Typescript and Rust, with SvelteKit and Tauri.

That's fair. The "no-tricks pricing" wording was taken 1-to-1 from the UI template I used :)

I'll update the copy, and try to explain the pricing model more clearly.

Also a good idea to make it possible to use one's own API key. I'll consider that.

It's GPT-3.5 only so far but I might add additional models at some point.

Right now it's pretty simple: First I drop the table/column information if the token limit gets exceeded otherwise (this is shown as a warning in the UI). Then if the limit still gets exceeded, the I show an error to the user.

I plan to make this process more smart eventually.

I'd like to use it eventually but as of now API usage is too limited.

I've had mostly the same experience as calmoo.

And when it does go wrong, I've had good success telling it what it did do wrong. It will usually correct itself then.

Correct, you probably should know SQL.

In my experience though it is often a significant time saver if I only have to review the output of the AI vs. coming up with everything myself.

Re: ambiguities: You are right, the AI won't always be able to infer the correct fields to use. In such cases though it is often enough to help the AI out a little. E.g. by saying "information X is stored in field Y of table Z".

Even if you have to do that, you can still save time and more importantly mental effort by letting AI help you, compared to writing all the SQL yourself.

Re: iterative process: You can simply send a follow up message saying "You did X wrong". It is usually happy to correct itself.

No, currently it doesn't.

This is a case where it could help to give the AI some example values of the actual data. The same applies for e.g. JSON fields.

I've been thinking about ways to make it possible for users to easily provide examples to the AI. Essentially that would mean selectively giving access for specific rows/columns to the AI.

Interesting idea. Do you have some examples of how you would like to use that, or maybe even an app where you'd like to integrate it?

Noted!

So far it's Mac only. If I can get some traction on this, I plan to support Windows and Linux eventually.

If I can get some traction on this, I plan to support Windows and Linux eventually.

They are made with https://www.screen.studio/

Correct. When you buy the lifetime license you get one year of the AI included, afterwards it is $49 per year for the AI then.

I should make that more clear on the website.

Thanks for the feedback, I'll try to improve that.

Thanks for reporting. I'll have a look what's missing.

Thank you!

It does use one common OpenAI AI account.

Thanks for the hints, typos should be fixed now.

Thanks for the hint!

Yeah I started with a landing page template from TailwindUI, then mixed in a few other building blocks also from TailwindUI, plus some customization.

For me, regular exercise got rid of the back pain that I used to get from working at a desk. This took about two months until I didn't feel any pain anymore. In those two months, I experienced more severe back pain though than I had before. As it turns out, this probably came from eating too many nuts.

So as I started working out more, I also began to eat more healthy, including lots of nuts every day. After a couple weeks of this, I started getting this intense pain in my upper back on the right side, which I never had like this before. I was having this pain for about two weeks and it was there constantly, no matter if I was sitting at a desk or not. Any massages that I got to address this didn't help.

According to a video (https://www.youtube.com/watch?v=jcrii9_Um0I), eating lots of nuts bloats up the gallbladder, which then presses on a nerve. This can lead to pain on the right side of the back and, although I didn't experience this, pain in the neck and headaches.

I then stopped eating nuts and the pain was gone two or three days later. Today I do eat nuts again. But if I eat lots of them every day for weeks on end, the pain does come back, although I never had it as severe again.

So maybe even though your pain tends to be on the left side, dietary changes could be worth a try.