This is a patch for 5.2.x to return a select()-able variable for a given
PostgreSQL connection.
PG allows ASync queries, pg_send_query, and notifications,
pg_get_notify. Currently (afaik), there is no way to add a PostgreSQL
socket to the event notification array in used with stream_select();
Hi Oskar,
Yes, you can use a plain array too.
I was just giving you a normal approach (ArrayAccess inherited class)
because you may want a special behavior under it too.
Forget SplObjectStorage docs they're outdated read the source! =)
Undoubtely devs will not mark spl_object_hash a E_DE
Hello Guilherme
The new implementation of spl_object_hash will solve it, since it's a
faster implementation than the old one.
Just one hint, you should not try to echo the generated hash, since it
may have non-printable chars.
I don't think that will be a problem...
Also, your code may stil
I think our bug current tracker is pretty good and most importantly
makes it easy to report and update bugs which is conducive to more
issues being reported. Often extra features of bug trackers make them
overly complex to use and people just get frustrated with them and
don't report bugs a
IMHO, the prefix will turn everything more readable...
I already saw people experiencing some doubts regarding this piece of
code. I had to illustrate it everything.
namespace Foo;
class Bar
{
public function test()
{
try {
do_some_stuf();
} catch (Exception $
Oskar,
The new implementation of spl_object_hash will solve it, since it's a
faster implementation than the old one.
Just one hint, you should not try to echo the generated hash, since it
may have non-printable chars.
Also, your code may still be possible to use SplObjectStorage.
Etienne did a lo
Of course being mentor for the past 2 years I want to be a mentor
again this year. But there are a few things we need to fix. I sent an
email to the other mentors about 3 months ago about things that went
"not-so-well" last year.
Here are a few things that were suggested and came out of this
"disc
