Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

On Wed, Oct 12, 2016 at 4:58 AM, Rowan Collins wrote: > On 11/10/2016 17:39, Lester Caine wrote: > >> The importance of 'null' in relation to SQL data sets is something that >> PHP seems to push under the carpet a bit. It is essential to the way SQL >> works and so needs

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

On 11/10/2016 17:39, Lester Caine wrote: The importance of 'null' in relation to SQL data sets is something that PHP seems to push under the carpet a bit. It is essential to the way SQL works and so needs to mirror properly which trying to emulate something without having the correct metadata

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

On 11/10/16 16:00, Adam Baratz wrote: >> I've had a quick look at the bug fix, although I haven't tested it. By >> > the looks of it, it seems that the third parameter has become mandatory, >> > which to me seems unacceptable. >> > >> > I would say that the type parameter should have precedence

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

> > I've had a quick look at the bug fix, although I haven't tested it. By > the looks of it, it seems that the third parameter has become mandatory, > which to me seems unacceptable. > > I would say that the type parameter should have precedence over the > actual PHP type only when it is

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

Hi Adam, On 04/10/2016 16:44, Adam Baratz wrote: > I'm happy to work on the bug fix. I'm leaning towards only applying it to > master in case others have coded around this behavior. I maintain > pdo_dblib, so I know that driver and its use cases pretty well. But since > this would affect more

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

Hi, On 04/10/2016 16:33, Christoph M. Becker wrote: > On 04.10.2016 at 16:20, Matteo Beccati wrote: > >> Hi, >> >> On 04/10/2016 16:15, Adam Baratz wrote: >> Well, I'm pretty sure Postgres won't be affected either way, because its type system is such that you can't prepare a query

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

> > > Well, I'm pretty sure Postgres won't be affected either way, because > >>> its type system is such that you can't prepare a query where the types > of > >>> parameters can't be decided yet. A query like this simply gives an > error. > > Firebird, oracle and mysql would have

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

On 04.10.2016 at 16:20, Matteo Beccati wrote: > Hi, > > On 04/10/2016 16:15, Adam Baratz wrote: >>> > Well, I'm pretty sure Postgres won't be affected either way, because >>> its type system is such that you can't prepare a query where the types of >>> parameters can't be decided yet. A

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

Hi, On 04/10/2016 16:15, Adam Baratz wrote: >> Well, I'm pretty sure Postgres won't be affected either way, because >> its type system is such that you can't prepare a query where the types of >> parameters can't be decided yet. A query like this simply gives an error. >>> >>> Firebird,

Re: [PHP-DEV] Fwd: [PHP-BUG] Bug #73234 [NEW]: emulated statementslet value dictate parameter type

> > >> Well, I'm pretty sure Postgres won't be affected either way, because > its type system is such that you can't prepare a query where the types of > parameters can't be decided yet. A query like this simply gives an error. > > > > Firebird, oracle and mysql would have exactly the same