I have opened a ticket (#1147) for the full_column_names issue, which is back in 3.1.3. pls check it out.
also, I noticed the following : when selecting from a view, and duplicate column names exist, there is an attempt to de-dupe them, by adding a sequence number, like this: ID ID:1 ID:2 etc this however does not happen with duplicate columns that are returned from a query. so, the statement: select * from master,detail where detail.masterID=master.ID and, create view v1 as select * from master,detail where detail.masterID=master.ID; select * from v1; do not have the same result wrt to column names. I feel this is inconsistent. you should either de-dupe all result sets (IMHO a bad idea), or leave all result sets alone, as far as names is concerned (my suggestion). I understand that this "column names" issue is becoming a pain for the sqlite authors, but OTOH, it is very important for wrapper authors...