On Fri, Apr 18, 2014 at 8:08 PM, Andy Goth <andrew.m.g...@gmail.com> wrote: > On 4/18/2014 12:29 AM, Max Vlasov wrote: >> >> So it seems like if general queries allow affinity automatical >> selection while bind api does not have the corresponent function. I >> know that I can analize incoming data myself, but since general >> queries use a similar function probably, making some kind of >> sqlite_bind_auto should be no big deal. But probably this decision was >> deliberate. > > > This was done for C compatibility. A C++ wrapper for SQLite can have an > sqlite_bind_auto() function which is overloaded for a variety of types, > but it would in reality be multiple functions that have the same name > but otherwise different type signatures.
I meant something different. A function accepting a text value while sqlite doing affinity conversion according to how the value "looks". Actually it seems that all the problems I faced was related to the type being typeless in declaration. For integer-declared fields sqlite correctly converts them to the integer affinity even with sqlite3_bind_text function. So it makes no sense to force other kind of detection if the type is declared. But if I stay with typeless fields, I will definitely will have problems with indexes on them, because seems like the query planner relies on declared types and doesn't care how many rows have particular affinity. So it looks like I should prescan some rows for type detection if I want an automatic conversion not knowing type info in advance Max _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
