Tim Bunce wrote:
> On Wed, Mar 10, 2010 at 10:25:45AM +, Martin Evans wrote:
>
>> 1. the TYPE attribute on a statement is clearly documented as to what it
>> should contain - "The values correspond to the international standards
>> (ANSI X3.135 and ISO/IEC 9075) which, in general terms, means
On Wed, 10 Mar 2010 13:57:07 +, Tim Bunce
wrote:
> The column_info() method maps to ODBC SQLColumns() function, and the
> type_info() method maps to the SQLGetTypeInfo() function.
> http://search.cpan.org/~timb/DBI-1.609/DBI.pm#ODBC_and_SQL/CLI_Standards_Reference_Information
FYI both links
On Wed, 10 Mar 2010 13:57:07 +, Tim Bunce
wrote:
> On Wed, Mar 10, 2010 at 10:25:45AM +, Martin Evans wrote:
>
> > 1. the TYPE attribute on a statement is clearly documented as to what it
> > should contain - "The values correspond to the international standards
> > (ANSI X3.135 and ISO/
On Wed, Mar 10, 2010 at 10:25:45AM +, Martin Evans wrote:
> 1. the TYPE attribute on a statement is clearly documented as to what it
> should contain - "The values correspond to the international standards
> (ANSI X3.135 and ISO/IEC 9075) which, in general terms, means ODBC".
>
> However, it
On Wed, 10 Mar 2010 10:25:45 +, Martin Evans
wrote:
> H.Merijn Brand and I have been talking this over on #dbi and Tim asked
> for a summary. I don't want to misrepresent what Merijn said, afterall
> he started the thread but I think it boils down to these issues:
>
> 1. the TYPE attribute o
On Wed, 3 Mar 2010 16:10:53 +0100, "H.Merijn Brand"
wrote:
> DBD::Oracle does not support column_info ()
As Martin kindly pointed me out that column_info () *does* work in
Oracle, but you need to spell out the table and fieldname in capitals.
Oracle--
This database doesn't seem to support mlsla
Martin Evans wrote:
> H.Merijn Brand wrote:
>> On Mon, 08 Mar 2010 10:13:02 +, Martin Evans
>> wrote:
>>
>> large original chunks snipped ...
>>
>>> H.Merijn Brand wrote:
I see a big difference in what $sth->{TYPE} returns (and the name) and
what column_info () - if implemented - is
