My point (which may not have been clear) was that when I explicitly told it that the versions of SQLite I'm using supports "returning," it still returned incorr

My point (which may not have been clear) was that when I explicitly told it that the versions of SQLite I'm using supports "returning," it still returned incorrect code. It did not use "returning", and repeatedly, even after being corrected, grabbed the row count instead of the column value. I understand that it's a language model - my point was that in my experience, the depth of training data just isn't there for alternative implementations. It can do the things you ask one way, maybe two or three, but if you know how you actually want something done you're probably better off writing it yourself (for now).