> Alan,
>
> I share the same feeling and too have been looking at ezsql, I have 2
> questions though, if you don't mind:
> 1 - I have not found any explicit handling for transactions
> 2 - Reading the source code there does not seem to be any provision to
> use stored procedures (apart from the selectable ones of course)
>
> Am I right ? and how did yousolved those ? (the developpers are not
> really responsive !)
> thanks in advance
> Didier
>

The developer (Justin) has been very responsive to me. And I have only
recently made a contribution to him for the excellent work and support.
Transactions are handled in two ways - 1. by default they occur at the
point when a page is delivered from the server. 2. By explicit calls to
start and commit/rollback them. I only start one manually in rare occasions
but I call commit/rollback explicitly when I need to send a location header
(server redirect) before the page is completed or when I detect an error in
the execution of query/SP Using the @ symbol provides for you to catch
exceptions and apply appropriate behaviour without displaying isc error
messages or the like. I use the ezsql database handle for everything I do in
this regard so I am using the same connection.
Stored procedures are also very simple to execute using the $db->getvar call
(I often return a code from my stored procedures in this context) or the
@ibase_query($db->dbh,"EXECUTE PROCEDURE etc where $db-dbh is the handle
generated by ezsql.

Alan