Dear PayPal customer,
It has come to our attention that when logging into PayPal,
you or somebody else have made several login attempts and reached
your daily attempt limit. As an additional security measure your
access to PayPal will be limited in a 24-hour period if you do not
verify your id
Hi Sean:
On Mon, Nov 08, 2004 at 10:32:57AM -0800, Sean Chittenden wrote:
>
> Bah, provide a backwards compatibility config option.
The PHP extension isn't a place for that. PDO or some database
abstraction layer written in PHP is.
Anyway, as mentioned, none of the DBMS's output a boolean dat
A boolean value is returned as the strings 't' and 'f', not the
constants true and false. This presents all kinds of interesting
oddities for code that does something like:
I suspect that behavior has nothing to do with PHP and everything to
do with PostgreSQL. Each DBMS outputs their information
On Fri, Nov 05, 2004 at 11:07:53AM +0100, Derick Rethans wrote:
> On Fri, 5 Nov 2004, Klaus Reimer wrote:
>
> > Marcus Boerger wrote:
> > > we've haered of it in the past but it was too late to add for 4.3
> > > series and obviously nobody cared to look for it for 5.0. So no the
> > > next versi
Same logic is applicable, in the event of failure false or invalid
resource maybe returned.
Ilia
Markus Bertheau wrote:
Ð ÐÐÐ, 08.11.2004, Ð 16:33, Ilia Alshanetsky ÐÐÑÐÑ:
The error functions do so because they are likely to be called if
creation of a connection fails so there may not always be
Ð ÐÐÐ, 08.11.2004, Ð 16:33, Ilia Alshanetsky ÐÐÑÐÑ:
> The error functions do so because they are likely to be called if
> creation of a connection fails so there may not always be a valid
> resource. The state checking function would presumably be only run on a
> valid connection and consequentl
The error functions do so because they are likely to be called if
creation of a connection fails so there may not always be a valid
resource. The state checking function would presumably be only run on a
valid connection and consequently should be strict about the resource
parameter (IMO).
Ili
Ð ÐÐÐ, 08.11.2004, Ð 16:04, John Coggeshall ÐÐÑÐÑ:
> if (zend_parse_parameters_ex(ZEND_PARSE_PARAMS_QUIET, ZEND_NUM_ARGS()
> TSRMLS_CC, "r" ..
>
> why would you silence the error for the parameter when this function
> requires a valid Postgres resource to do anything?
I copied the behaviour
if (zend_parse_parameters_ex(ZEND_PARSE_PARAMS_QUIET, ZEND_NUM_ARGS()
TSRMLS_CC, "r" ..
why would you silence the error for the parameter when this function
requires a valid Postgres resource to do anything?
John
On Mon, 2004-11-08 at 07:44, Markus Bertheau wrote:
> Hi,
>
> attached is a p
Hi,
attached is a patch which implements a function pg_result_sqlstate. This
function is needed because the error messages returned by
pg_result_error is localized and can therefor not be parsed reliably.
The patch is against PHP5. Barring any objections please apply the patch
for PHP 5.0.3.
Tha
Hi,
some time ago I prepared a patch that corrects a bug in the printf
family of functions. The patch makes printf not throw a warning about
too few parameters when there really are enough parameters.
The patch itself is at
http://www.bluetwanger.de/~mbertheau/formatted_print.c.patch and is for
P
MB>>Adding an argument would be a major BC but sure is_null($this) would work,
MB>>only it would be another big slowdown.
I don't think 2-3 additional opcodes are a "big" slowdown - if you are
using non-default ctors and accessors anyway, you probably are doing
something order of magnitude bigge
Hello Stanislav,
Monday, November 8, 2004, 11:29:13 AM, you wrote:
MB>>> you won't be able to tell from inside __call() whether a static or
MB>>> non static method was meant.
> Technically, it's not a big problem IMO - there could be an argument added
> or some other solution, like presence of $
MB>> you won't be able to tell from inside __call() whether a static or
MB>> non static method was meant.
Technically, it's not a big problem IMO - there could be an argument added
or some other solution, like presence of $this.
MB>>non static method was meant. The same holds for __get() and __
Hello Timm,
you won't be able to tell from inside __call() whether a static or
non static method was meant. The same holds for __get() and __set().
Also if we start using such code we'd need a class constructor. Thus
this dicussion is leading to the following set of new magics:
__static_get
__s
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (448 total including feature requests)
===[*Compile Issues]==
28103 Open During ./configure you get png error instead of iodbc
28700 Open yaz recode conflic
Hi All,
BC is a good thing when you want to keep maintenance down and developers happy
but sometimes stalls progression. When there are bugs in the code that have been
there for a while, chances are that they will stay there forever for BC
reasons. The latest example is the postgreSQL driver, but
17 matches
Mail list logo
