On Jul 12, 2007, at 11:12, Greg Sabino Mullane wrote:
Not sure - just a plain "CANCEL" or "WAIT" might be a little
confusing, no?
These are kind of syntactic sugar left over from earlier
development anyway,
as the (I suppose) canonical way to do it will be to cancel or wait
yourself
with pg_cancel and pg_result.
Ah, yes, I knew that there was a better way. I like that much better.
Glad you like it, it's been a struggle to fit into the DBI way of
doing
things. I'd really like it if execute() took attribs, so we could do
an async per execute, not prepare. Other possible options include a
custom
execute method (pg_execute) or flipping a global attrib before the
execute ($dbh->{pg_async}). I'm open to any and all API changes and
suggestions.
Doing it in prepare() rather than execute() doesn't bother me,
personally. I think that I'd likely either always or never use it for
a given query.
Best,
David
