> -----Original Message-----
> From: Tim Bunce [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, January 20, 2002 2:16 PM
> To: Sterin, Ilya
> Cc: [EMAIL PROTECTED]
> Subject: Re: bind_param()
>
>
> It would have to be a new method. Perhaps
New method is fine, I don't see a problem with it. Though I thought
about just differentiating between refs and vals in the bind_param
version, therefore this will make it kind of a seemless interface. I'm
not sure about underlying obstacles for this though.
Maybe I'm going a little overboard here, but something that will allow
both types, would be nice as well. Possibly some values will change and
some won't, therefore the binding of the ref will be delayed, but the
values can be bound right away?
What do you think?
>
> bind_param_at_execute(...)
> bind_param_lazy(...)
> bind_param_ref(...)
>
> The driver could just defer the actual bind till execute is
> called. I might just be able to get the Driver.xst template
> code to handle that automatically.
I wish I would have some time to look at it. If I do sometime next
week, I'll let you know and probably ask a >>few<< questions as well:-)
I still have the preparser on my list of things to test, so I'll have to
do that first.
Ilya
>
> >>todo
>
> Tim.
>
> On Sun, Jan 20, 2002 at 12:47:13PM -0800, Sterin, Ilya wrote:
> > Would it be worth while to redo bind_param() to allow it to except
> > both references and values, therefore allowing to execute with
> > different values, based on the changing values of the
> variable? Will
> > this somehow be effected with the way Perl might reallocate the
> > pointer and assign a different address to the scalar,
> though I believe
> > the references are then updated as well with the new
> properties? Or
> > is there some catch to it? It must be since I haven't heard this
> > brought up before.
> >
> > Ilya
>
