31–40 of 48 posts
If you can export your data to SQLite first (my https://datasette.io/tools/db-to-sqlite tool can help with that) you can upload the SQLite database directly to ChatGPT Code Interpreter and have it run the queries for you, since sqlite3 is in the Python standard library If you do this, it will automatically retry with a new SQL query if it gets any error messages.
0 - https://chat.openai.com/share/5534e0b2-4010-4da6-99b9-a3aa02...
If you know SQL why is this better than just writing SQL? If you don’t know SQL how do you know it’s correct? I had to forbid my coworkers from using chatgpt to generate SQL because it kept doing things slightly wrong - like missing parens when dealing with AND and OR in a where statement.
> If you know SQL why is this better than just writing SQL? If you don’t know SQL how do you know it’s correct? You test it. And what do you mean by “know SQL?” No one knows everything about SQL. Virtually everyone writing SQL is in between the two extreme cases you provide.
Earlier quoted context omitted.
Most people can read more complicated text than they can write. Most people who need to generate a query can run it and look at the results. I use chatgpt to help me, particularly with languages I don’t write in everyday. And I often find myself arguing with chatgpt that what it wrote is wrong, because I can read the query, but don’t know how to write the query I need.
I agree with your sentiment but it actually occurred to me that code might actually be the reverse - where you can write more complicated code than you can read.
I guess it can go either way. Sometimes ChatGPT4 is great and saves me time, but the cycle of "explain what I want, get the output test/compile it, post the errors, try again" doesn't always converge quickly enough to not be more irritating than actually learning the issues in the code I'm trying to interface with. So I'll try it a bit, but if it goes back and forth more than 3 or 4 times, I'll give up and dig in to study the thing.
I've spent a lot of time on this problem space for our business. My current conclusions are as follows: Writing the actual SQL query is not the hard part for us. The hardest part is exhaustively expressing our intention in any language at all , followed closely by its apprentice - the incomplete requirements monster. I've found that if I can coach a team member into giving me a proper natural language statement that…
I've spent a lot of time on this problem space for our business. My current conclusions are as follows: Writing the actual SQL query is not the hard part for us. The hardest part is exhaustively expressing our intention in any language at all , followed closely by its apprentice - the incomplete requirements monster. I've found that if I can coach a team member into giving me a proper natural language statement that…
>>* ...Anything serious...* My problem is that I simply cannot trust any data coming from GPT - it doesnt have real-time info, it constantly tells me what it CANT DO and its never able to tell me what it CAN DO. The platform is extremely powerful, and what we are seeing is that the cadre of AI LLMs/apps that are coming about has all the devs/companies frantically running in a panic on how to both weaponize and moneti…
I just used it to write shell function which extracts value from .ini file using section, name as a parameters. Works perfectly. Otherwise I would have to manually dick with awk input string wrecking my brain in the process
Earlier quoted context omitted.
>>* ...Anything serious...* My problem is that I simply cannot trust any data coming from GPT - it doesnt have real-time info, it constantly tells me what it CANT DO and its never able to tell me what it CAN DO. The platform is extremely powerful, and what we are seeing is that the cadre of AI LLMs/apps that are coming about has all the devs/companies frantically running in a panic on how to both weaponize and moneti…
>"My problem is that I simply cannot trust any data coming from GPT" I just used it to write shell function which extracts value from .ini file using section, name as a parameters. Works perfectly. Otherwise I would have to manually dick with awk input string wrecking my brain in the process
I would EXPECT/DEMAND your results - other results are not functions.
> "What happened to the company?" > "It collapsed because nobody knew how to maintain the queries—they generated everything with ChatGPT."
> "What happened to the company?" > "It collapsed because nobody knew how to maintain the queries—they generated everything with ChatGPT."
Earlier quoted context omitted.
> If you know SQL why is this better than just writing SQL? If you don’t know SQL how do you know it’s correct? You test it. And what do you mean by “know SQL?” No one knows everything about SQL. Virtually everyone writing SQL is in between the two extreme cases you provide.
If you understand SQL enough to know if the query ChatGPT produced is valid - you probably could have written it yourself. I don’t see how prompting chatgpt and testing its results is faster or better than just writing SQL.
Like I said, you need to test it. Not read it. Test it.