I just tested this on postgresql and I always get unqualified column names as I would expect.
I remember this was a lot worst in previous sqlite versions and I needed to play with two compile time/pragma flags and depending on that combination we got some bizarre results. I understand that there is legacy code that should take in consideration when changing sqlite behavior. But like it's already done on several other cases why not fix this issue and wrap this fix with "#ifdef SQLITE_CLEAN_COLUMN_NAMES" that's not defined by default so older code will remain working but new code can enable this and use it ? ? Cheers ! ? -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: URL: <http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/attachments/20150826/c146229d/attachment.ksh>
