Yeah many rough edges indeed. The generated SQL is the plain output from GPT-3; I have not done anything to customize the model or validate syntax outside it, so the roughness is expected. No idea if folks will find value in this despite that, hence the demo.

Definitely passes the 'is it interesting' test. Certainly passes the 'should dig deeper' gate. Well done. I like to think I have a solid sql understanding but it's also nice to be able to ask questions in a natural language.

I'm still amazed that I can type a natural language phrase into google and often get sensible results.

Awesome! Always happy to chat; my contact info is in my profile (and also at the bottom of the linked demo).

Cool! Yes, the ability to customize the model (https://openai.com/blog/customized-gpt3/) also seems like it could be really useful for this.

Clickable link: https://app.tabbydata.com/sql-assistant-demo

In terms of actually tracking and charting this data, it’s pretty useful to have it all in one place and queryable by SQL—this is not usually the case by default!

I built https://www.tabbydata.com for SaaS founders who have this problem.

This is a great overview of what to measure, at least for business metrics.

(Shameless plug…) For folks wondering how to measure, and also how to track product metrics for their SaaS, I wrote a thing: https://www.tabbydata.com/book

I think this is why most sites—especially those targeting technical audiences—should rely on server-side analytics instead. Add some middleware to your web framework of choice which logs request data and parse that, or use something like https://www.tabbydata.com (disclaimer: I built that) to pipe it into a data warehouse. Voila! No JS tracking, retain useful metrics.

I’ve used server log analysis, awstats, for maybe 20-25 years. It’s really interesting the difference between awstats and Google analytics (or Adobe analytics, etc).

The reason I keep using Google stats on my backend is convenience and “Google magic” for tracking session length, bounce, behavior, etc etc. I can get most of that out of awstats, but that requires more work.

And how did you verify its integrity? And what is the upgrade path?

The releases are signed with well-known keys.

But if you don't trust the devs you'll need to use other software, yes.

Based on the argument given, looks like a fair take to me.

n8n and Node-RED are both really neat! Over the break I built a little project that takes a different approach; for me the schleppy part of API integration is not usually the code but it's the infrastructure (where to host for cheap, with a simple deploy pipeline, maybe scheduled execution, etc). https://www.tabbydata.com/glue is a little thing I built so that I don't need to think about those things again.

Have you tried Autocode [0] for these use cases? I think you'll find it provides exactly what you need and more. Disclaimer: am founder.

[0] https://autocode.com/