--- On Thu, 2/10/11, Puneet Kishor <punk.k...@gmail.com> wrote: > Date: Thursday, February 10, 2011, 10:35 AM > > On Thursday, February 10, 2011 at 9:22 AM, Nißl Reinhard > wrote: > > Hi, > > > > I'm sorry Pavel, I think you've got me wrong. > > > > > It's not "buggy". Name of the column in result > set is not defined > > > unless you use "as". > > > Pavel is not wrong. SQLite is not buggy. Your expectation > of what it should do is at fault here. > > .. > > > I used to think as you too, but then learned otherwise. The > developers simply didn't add the code to dependably > determine what the column should be called, because, > surprisingly (or not surprisingly, if you think about it a > bit), that code would be very complex to cover all the > possible cases. The simplest solution is to depend upon AS > aliasing, else, do something undependable (to us). > > Puneet. >
Not only is it complex, but as I recall, back when the developers did try to be consistent in how column names were presented, no matter how they coded it, someone would pipe up with an opinion that it should be done another way. There were pragmas to try to get the column names to match different expectations. In the end, they decided to just call it undefined and let the user use AS to get what they wanted. I think that was the right decision. David _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
