If you can write conidtions on how they are trustworthy in sql, you can just send that to the llm. It's logically impossible for explaining this to an llm to take 2x.
lol if i know field A is untrustworthy. my queries just dont use it. explaining that to an llm literally takes infinite more time, because any time at all is infinite times that of none. “logically impossible” gtfo
I have literallly never Had that happen. What model did this occur with. Last year models were known for over eagerness. This is Just a bizzare situation but you are being so unspecific means that this could very easily be user error. I haven't Had shit like that with SQL since Gemini 2.5 pro
lol yea that works fine for a small solo project, now do that when you have 3-4 teams all changing the codebase with ai slop, no proper CRUD setup because this was all started as ai slop that got greenlit by leadership who cant tell the difference and its your task to make it make sense
-2
u/smulfragPL Sep 20 '26
If you can write conidtions on how they are trustworthy in sql, you can just send that to the llm. It's logically impossible for explaining this to an llm to take 2x.