On Wed, Nov 3, 2010 at 8:25 PM, Wez Furlong wrote:
>
> On Nov 3, 2010, at 9:52 PM, Stanley Sufficool wrote:
>
>> Before I gut PDO_DBLIB one more time to implement native parameter
>> binding for stored procedures, what are the thoughts on returning the
>> column values from the database as the nat
On Nov 3, 2010, at 9:52 PM, Stanley Sufficool wrote:
Before I gut PDO_DBLIB one more time to implement native parameter
binding for stored procedures, what are the thoughts on returning the
column values from the database as the native PHP type when possible?
Currently everything is returned as
Before I gut PDO_DBLIB one more time to implement native parameter
binding for stored procedures, what are the thoughts on returning the
column values from the database as the native PHP type when possible?
Currently everything is returned as a string, incurring overhead for
conversion and creating
Hi!
What would happen if the string contained a matching pattern twice or
me, which would be 'returned', also does this allow the rest of the
string to be pretty much junk.
Yes, the rest of the string (i.e. everything after the format was
matched, while ignoring +) can be anything. I.e., as so
I think you will need to push for their inclusion (involving
requesting svn access and doing it yourself) precisely because there
is no one is currently looking after the extension.
Chris
On 10/23/2010 12:46 AM, Jorrit Kronjee wrote:
Chris and others,
Since SNMP didn't have any unit tests to
>
> Yes, there is a reason:
>
> As it was explained before, lemon would not display token names but
> actual token "values". So instead of "Unexpected T_PAABLAH" it would say
> "Unexpected '::' ..."
>
hello,
value of some tokens is not what would be expected either. Think a bit about
T_STRING for
Like the idea,
Couple of questions...
What would happen if the string contained a matching pattern twice or me, which
would be 'returned', also does this allow the rest of the string to be pretty
much junk.
(haven't had time to test patch as miles from a computer)
--
James Butler
Sent from my
Hi!
As I previously noted, in DateTime module there's no way to make
DateTime format parser to parse the string if the string contains more
data that the format supplies - i.e. if you need 'Y-m-d' and you have
string '2010-11-02 12:30' - you can't make DateTime accept it without
pre-parsing.
It has been a while since the last releases in the stable branches of
PHP and it is time to get the process going once again. This e-mail is
a 2 week notice prior to the RC1 for both versions, the goal is to
have the final releases completed by mid-December.
As far as PHP 5.2 is concerned 5.2.15 i
> > Until version 5.3.2 this worked fine, starting from version 5.3.3
>> parent::getFoo() calls __callStatic() instead of __call().
>>
>> This is a really bad BC change which i thought you decided to accept only
>> in minor versions change and not patch-level versions change.
>>
>> Anyway, I would
10 matches
Mail list logo