-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Umm, looking at that it strikes me that if someone calls
>
>bind_param( 1, $value, SQL_INTEGER ); # or { TYPE=>SQL_INTEGER }
>
> and the drivers translates that into *just* it's oen private type
> then valuable information has been lost.
>
On Mon, Oct 13, 2008 at 07:52:06PM +0100, Martin J. Evans wrote:
> Martin Evans wrote:
>> Thanks to all who have responded with clarification. I have implemented
>> ParamTypes in DBD::ODBC as a hash reference with parameter number as key
>> and each value is a hash reference with keys of 'TYPE' a
Martin Evans wrote:
Thanks to all who have responded with clarification. I have
implemented ParamTypes in DBD::ODBC as a hash reference with parameter
number as key and each value is a hash reference with keys of 'TYPE'
and values of SQL type number.
This will be in 1.17_2.
Martin
One last t
On Mon, Oct 13, 2008 at 11:53:34AM -, Greg Sabino Mullane wrote:
>
> > So { '1' => 'integer' } sure looks like a bug.
>
> >> However, bind_param currently saves the value to an internal form, without
> >> saving how it got there, which makes the key of that inner hash ('pg_type')
> >> difficu
Thanks to all who have responded with clarification. I have implemented
ParamTypes in DBD::ODBC as a hash reference with parameter number as key
and each value is a hash reference with keys of 'TYPE' and values of SQL
type number.
This will be in 1.17_2.
Martin
--
Martin J. Evans
Easysoft Lim
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> So { '1' => 'integer' } sure looks like a bug.
>> However, bind_param currently saves the value to an internal form, without
>> saving how it got there, which makes the key of that inner hash ('pg_type')
>> difficult to show. Because the valu
On Mon, Oct 13, 2008 at 08:38:08AM +0200, H.Merijn Brand wrote:
> On Sun, 12 Oct 2008 21:25:12 +0100, Tim Bunce <[EMAIL PROTECTED]>
> wrote:
> > On Sun, Oct 12, 2008 at 02:55:51AM -, Greg Sabino Mullane wrote:
> > >
> > > > values are hashrefs of type information in the same form as that
> > >
On Sun, 12 Oct 2008 21:25:12 +0100, Tim Bunce <[EMAIL PROTECTED]>
wrote:
> On Sun, Oct 12, 2008 at 02:55:51AM -, Greg Sabino Mullane wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: RIPEMD160
> >
> >
> > > values are hashrefs of type information in the same form as that
> > > pro
On Sun, Oct 12, 2008 at 02:55:51AM -, Greg Sabino Mullane wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
>
> > values are hashrefs of type information in the same form as that
> > provided to the various bind_param() methods
> ...
>
> > I'm not sure why the values of the
On Sun, 12 Oct 2008 02:55:51 -, "Greg Sabino Mullane"
<[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
>
> > values are hashrefs of type information in the same form as that
> > provided to the various bind_param() methods
> ...
>
> > I'm not sure why t
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> values are hashrefs of type information in the same form as that
> provided to the various bind_param() methods
...
> I'm not sure why the values of the keys are hash references unless
> multiple values are to be stored. If multiple values pe
H.Merijn Brand wrote:
On Fri, 10 Oct 2008 16:19:20 +0100, Martin Evans
<[EMAIL PROTECTED]> wrote:
Hi,
The DBI specification for ParamTypes taken from the DBI pod says the
following for ParamTypes:
Returns a reference to a hash containing the type information currently
bound to placeholders
On Fri, 10 Oct 2008 16:19:20 +0100, Martin Evans
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> The DBI specification for ParamTypes taken from the DBI pod says the
> following for ParamTypes:
>
> Returns a reference to a hash containing the type information currently
> bound to placeholders. The keys
Hi,
The DBI specification for ParamTypes taken from the DBI pod says the
following for ParamTypes:
Returns a reference to a hash containing the type information currently
bound to placeholders. The keys of the hash are the ’names’ of the
placeholders: either integers starting at 1, or, for
14 matches
Mail list logo
