sqlite3_column_name would be favorite, assuming that the DBD provider uses
the prepared statements API (which it should be doing).

Clay Dowling

Joe Casadonte said:
> On Wed, 27 Dec 2006, Clay Dowling wrote:
>
>> If you use the SQLite API rather than shelling to the SQLite command
>> line utility you may get more satisfactory results.  The API between
>> 2.x and 3.x is quite different, but the column headers are readily
>> available.
>
> I actually need this capability in the DBD::SQLite Perl module; I was
> using the command line tool as an example.  What can I look for in the
> API, to point the DBD::SQLite maintainer at?  Thanks for the help!
>
> --
> Regards,
>
>
> joe
> Joe Casadonte
> [EMAIL PROTECTED]
>
>
> -----------------------------------------------------------------------------
> To unsubscribe, send email to [EMAIL PROTECTED]
> -----------------------------------------------------------------------------
>
>


-- 
Simple Content Management
http://www.ceamus.com


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to