The user using your wrapper needs to be smart enough to know what he is doing. Your stuff should be merely the conduit not the editor. If I attempted to use a wrapper that "messed" with my SQL code, it would immediately be my ex-wrapper.
Fred -----Original Message----- From: Tim McDaniel [mailto:[EMAIL PROTECTED] Sent: Monday, February 28, 2005 2:43 PM To: sqlite-users@sqlite.org Subject: RE: [sqlite] ticket 1147 > I'll third Dr. Hipp's statement. > > I have my own wrappers (in Perl), made for public > consumption, and never had problems with returned column names. > > 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. > > Insisting on using default names all the time is for uber-lazy users. > > -- Darren Duncan > As a wrapper writer, I cannot control the SQL that a user of my wrapper is passing in. Tim
