[Idea] ChatGPT integration

[marckohlbrugge]

I love Blazer but I always struggled having to write complex SQL queries. I was too used to ActiveRecord’s simple interface.

These days I have ChatGPT write my Blazer SQL queries. It works surprisingly well.

Is there any interest in adding a native ChatGPT integration into Blazer?

The way I envision it is that users can configure their OpenAI key, add the openai-Ruby gem, and the Blazer “New query” interface will have an extra textarea that will submit to a new controller which calls the ChatGPT API and returns an SQL query.

A full back-and-forward chat interface is probably out of the scope of Blazer, but a one-shot approach should cover most use cases.

[sanfranciscocarrot]

+1 On this thread. I wonder if there is any possibility of strengthening the plotting capability/query improvement capability using this chatgpt

[coorasse]

We recently included it in our fork at https://github.com/renuo/blazer
I can open a PR if this looks interesting to the maintainer.
How it works:

• we add a prompt field
• the prompt is sent to openAI together with the database schema
• a query is received back.
• we try it and see if it executes successfully.
• if it does not, we give back the error to openai and ask to fix it. ww iterate maximum three times
• at the end we prefill the query with the result

We have been really happy with the result so far.

[jnunemaker]

This would be awesome. It would encapsulate a work flow I already use and save me the copy/paste back and forth. I've thought about adding it in. @coorasse interesting to see your approach. Thanks for sharing.

[knagode]

I think this is great. Could me merge this into main repo?

[knagode]

@coorasse I tried https://github.com/renuo/blazer but it has extra dependencies. I bumped into this:

Gem Load Error is: cannot load such file -- bootstrap/engine

Then I added gem: gem 'bootstrap' and ended up with:

The asset 'blazer/bootstrap.css' was not found in the load path.

It would be great if gem wouldn't have so many dependancies. Any idea how to proceed?

It would be great if you open Issues section on the repo so we can chat there further.