Yasuo Ohgaki wrote:
Wez Furlong wrote:
Regardless of whether it's a good idea or not, you should not just go
ahead and commit such a big behaviour change to the stable branch
during the release process.
Please revert your commit.
That's good point.
Any people should not depend on pg_execute's
sorry the word abuse pissed me off. I'm not abusing anything the protocols
weren't designed to support (even if they don't know it, but then, they do know
it). I can understand if nobody ever thought of this use of it before and is
why there is no support for using fcgistdin with php, even tho
Hi Rasmus!
Rasmus Lerdorf wrote:
I ran some tests, and did the following:
$Order_Total = sprintf("%01.20f",$Order_Total);
$Refund_Amount = sprintf("%01.20f",$Refund_Amount);
which produced:
$Order_Total = 102.84431566
and$Refund_Amount = 102.85
> PS: will a 64 bit INTEGER make it into PHP6?
But they're already here in fives-ville...
I recently had a regression test failure on our framework when testing on
the new AMD64 test server. The 'failed' test was expecting to see an error
when dealing with UNIX epoch timestamps after 2038. Of
Leon Matthews schrieb:
PS: will a 64 bit INTEGER make it into PHP6?
But they're already here in fives-ville...
I recently had a regression test failure on our framework when testing on
the new AMD64 test server. The 'failed' test was expecting to see an error
when dealing with UNIX epoch time
Lukas Smith wrote:
> Sorry but your comparison to file_exists() is wrong. pg_execute()
> compares to something like include() if at all. Again I do want
> something like pg_is_prepared() but I rather wait until pgsql 8.2 where
> we get a proper native solution.
>
> For your case you should simply
Is it ok to commit it to PHP_5_1?
The fix is just rase error after PQClear(). (i.e. change the line of
PHP_PQ_ERROR after PQClear())
--
Yasuo Ohgaki
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
If you're that familiar with the fcgi spec, then you'll realize that a
simple dup2() is not sufficient.
It's still better to tackle the problem "the right way" instead of
trying to force something to work in a way that it doesn't. Hence the
term "abuse".
Advocating the use of threads to "solve"
Sorry for sending twice wez, I meant to send it here in the first place.
No I'm not familiar with the fcgi spec.. I just by myself wrote an fcgi
interface, that's all.
ok you're right, _just_ a dup2 would be insufficient, even if it uses
pipes behind the scenes it's not much different from belo