ingres_close
Hi,
this might be obvious for the more enlightened among us, alas, I had to learn it the hard way (and I hope my interpretation is right):
WHENEVER you use ingres_commit(), you cannot use any other ingres-commands for this connection anymore, since ingres_commit() closes it. That means that any ingres_fetch_row/object/whatever has to come before the ingres_commit-call. I first thought, each ingres_query() had to be "committed", but that was wrong.
ingres_commit
(PHP 4 >= 4.0.2, PHP 5 <= 5.0.5, PECL ingres >= 1.0.0)
ingres_commit — Commit a transaction
Descrição
bool ingres_commit
( resource $link
)
ingres_commit() commits the currently open transaction, making all changes made to the database permanent.
This closes the transaction. A new transaction can be opened by sending a query with ingres_query().
You can also have the server commit automatically after every query by calling ingres_autocommit() before opening the transaction.
By default Ingres will roll back any uncommitted transactions at the end of a request. Use this function or ingres_autocommit() to ensure your that data is committed to the database.
Parâmetros
- link
-
The connection link identifier
Valor Retornado
Retorna TRUE em caso de sucesso ou FALSE em falhas.
Veja Também
- ingres_query() - Send an SQL query to Ingres
- ingres_rollback() - Roll back a transaction
- ingres_autocommit() - Switch autocommit on or off
User Contributed Notes
ingres_commit
ingres_commit
burckhardtNOSPAM at CUTMEgsf dot de
23-Jan-2002 03:00
23-Jan-2002 03:00