Hi,
Async. functions are introduced in the 5.1.0 release, but in my
opinion, there doesn't exist any supportive functions to use 'em.
Let's discuss this on an example:
if (!pg_connection_busy($dbconn)) {
pg_send_query($dbconn, "select * from authors; select count(*) from
authors;");
}
$res1 = pg_get_result($dbconn);
Above example is brought you from the official pg_get_result()
documentation.
1. How will we learn whether the data arrived from server or not?
There doesn't exist any PQsocket() similar function to make
a socket_select() call on it.
There're two ways to solve this problem:
1.1. Pray god to make our queries finished before calling
pg_get_result().
1.2. Enter to an endless loop bounded by pg_connection_busy().
Furthermore, you're free to try any adhoc sleep() method
inside the loop. (Recommended way in the documenation.)
IMHO, this is a very important missing property in the async.
functions. Without this, there shouldn't be any place of async.
queries in a production server.
2. What if we couldn't transmit whole data out of socket? Is there
any equivalent for PQflush() or PQconsumeInput()? Yes, there're
some places in the code which hold PQconsumeInput() calls, but
shouldn't it be better if we'd mention about this in the
documentation?
Other issues:
3. Can somebody explain me the existence of non-standard
pg_select(), pg_insert(), pg_update() and pg_delete() functions?
Are there any equivalent of these functions in other PHP
interfaces? Anyway, this is not the matter. What's the targeted
crowd in the implementation of these functions? Are there
any stuff we cannot achieve without using these functions?
4. I don't want to mention about the not described properties in
the documentation. (For instance, pg_select() function's options
parameter.)
Regards.
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
