Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In my experience LLMs excel at SQL.


If that's the case how would the sqlite package (also part of sqlean)'s fileio work out

https://github.com/nalgeon/sqlean/blob/main/docs/fileio.md

    fileio_read - Read file contents as a blob.
    fileio_scan - Read a file line by line.
    fileio_write - Write a blob to a file.
    fileio_append - Append a string to a file.
    fileio_mkdir - Create a directory.
    fileio_symlink - Create a symlink.
    fileio_ls - List files in a directory.

If one only exposes sqlite command query access and limit certain aspects of this sqlite extension depending on the use case perhaps, I feel like this might be a good alternative as well?

Edit: thinking more about it I think its for actually making sqlite interact with the filesystem and not the idea of it acting as a file system itself without too much overhead, I was thinking something like the sqlite database itself stores data and then we could do these operations fileio etc. but this isnt possible from what I could gather.

perhaps this might be more interesting https://github.com/narumatt/sqlitefs but what I mean is if something like the merge of fileio + sqlitefs where things dont have to go through fuse in general if that makes sense hopefully

Maybe I went a little tangential but sqlite is really awesome


Gemini 3 is very good in particular. Haven't had a serious attempt with GPT 5.2 yet, but I expect it to also be good (previous versions were surprising at times, e.g. used a recursive CTE instead of window functions). Sonnet 4.5 sucks. Haven't tried Opus for SQL at all.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: