On Mon, 8 Mar 2010 06:01:57 -0800 (GMT-08:00), Todd Zervas
wrote:
> Well, yes, but only the general comment that these catalog methods ought
> to return consistent values across different types of underlaying
> databases/drivers.
>
> And, I'm looking forward to the Unify implementation and the a
Well, yes, but only the general comment that these catalog methods ought to
return consistent values across different types of underlaying
databases/drivers.
And, I'm looking forward to the Unify implementation and the associated docs as
well :)
Todd Zervas
tazer...@earthlink.net
-Origina
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 returning.
>> I don't think
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 returning.
>
> I don't think I do with DBD::ODBC (results be
H.Merijn Brand wrote:
> I see a big difference in what $sth->{TYPE} returns (and the name) and
> what column_info () - if implemented - is returning.
I don't think I do with DBD::ODBC (results below).
> From the DBI docs:
>
>Handle attributes:
>
>"TYPE" (array-ref, read-only)
>
>
On Wed, 3 Mar 2010 16:10:53 +0100, "H.Merijn Brand"
wrote:
> I see a big difference in what $sth->{TYPE} returns (and the name) and
> what column_info () - if implemented - is returning.
Does no-one have an opinion on this?
I'd like to finish the Unify implementation.
And maybe even add some do
Tim Bunce wrote:
> On Sun, Mar 07, 2010 at 10:29:29AM -0800, David E. Wheeler wrote:
>> On Mar 7, 2010, at 5:43 AM, Tim Bunce wrote:
>>
Looks good, thanks. Pity you removed the `$dbh->{private_myapp_sql_mode}`
bit, though, as that's required when using C, which
you almost certainly a
