On 2015-03-02 04:51 PM, Paolo Bolzoni wrote: > I kinda get your point, but still we are speaking of the C interface > all the time. Sure in other contexts, like the TCL/SQL, the indexes > start from 1. However the bind and the column function are both in the > C interface.
It's when the C interface (or API) refers to items indexed by the SQL that's the odd child - it will cause much greater confusion if you bind in SQL ?1,?2,... and then the API binds or refers to those as col[0],col[1],... in stead of col[1],col[2],... This is what I meant with the API following the TCL convention in certain cases. In the ones where there are no TCL/SQL obfuscation it indexes like any C API to 0-based ranges. Yeah - it's still not nice, but I'm not sure any other way would be better.
