> > Simply put, the elegant solution for wrapper authors is to always use > 'as' to explicitly define the column names you want. You always know > how these names map to original table columns because you explicitly > said so.
It isn't as simply as that. I.e. within the Delphi wrapper users can apply theire own sql statement and it is binded to data-aware components showing content. To be able to do so, Delphi must assume certain data-types which is extracted from the metadata supplied by the api set. If duplicate names are supplied (like it is possible now) the wrapper must detect and change names, i.e. by adding a suffix _number. The 'as' surely helps a lot, but wrappers cannot always rely on that. I personally do not have any problems with the current sqlite implementation. But I suggest that before publishing the official release a pre-release is published for wrapper writers to allow them to addapt early. I.e. one or two weeks. I don't know about others, but we received a lot of complaints about bugs in our components using the latest sqlite release. It supprised us, needed to investigate, change sources and re-publish. It wasn't a big deal after all, but some of our users where frustrated by the isue. I would welcome an api set for retrieval of sql query metadata. The fact that users can change pragma will not have influence on the working of wrappers any more then. albert drent aducom software
