I picked up this thread in the LinksSQL Forum...
>No, but if you don't call disconnect() first, you will see errors in your error_log like:
>Issuing rollback() for database handle being DESTROY'd without explicit disconnect().
>You should always call disconnect() before you destroy a database handle. This is very important on other databases like Oracle, MS SQL 7, but not so on mysql (you just get warnings).
I too am getting this error in my error_log at:
>Issuing rollback() for database handle being DESTROY'd without explicit disconnect() at [snip]/db.cgi line 83.
The thread I snipped this from talked about running two LinksSQL databases together, but I am just running dbsql and another unrelated mysql database, each has their own name.
Just so I don't mess something up, where should I put the disconnect call and what would the proper format be?
--Stephen
>No, but if you don't call disconnect() first, you will see errors in your error_log like:
>Issuing rollback() for database handle being DESTROY'd without explicit disconnect().
>You should always call disconnect() before you destroy a database handle. This is very important on other databases like Oracle, MS SQL 7, but not so on mysql (you just get warnings).
I too am getting this error in my error_log at:
>Issuing rollback() for database handle being DESTROY'd without explicit disconnect() at [snip]/db.cgi line 83.
The thread I snipped this from talked about running two LinksSQL databases together, but I am just running dbsql and another unrelated mysql database, each has their own name.
Just so I don't mess something up, where should I put the disconnect call and what would the proper format be?
--Stephen