On 14/06/10 12:50, Elias Ghanem wrote:
SELECT INTO DUMMY DBLINK_EXEC(''CONNECTION_STRING TO DB3',
''UPDATE IN_FICHE_PRODUIT SET VALIDE = 1'');
If there's more than one value in that table, an explicit ORDER BY might
help (otherwise you could get the situation where query A will update
On 25/06/10 16:59, Rajesh Kumar Mallah wrote:
when i reduce max_connections i start getting errors, i will see again
concurrent connections
during business hours. lot of our connections are in transaction state> during business
this peculiar behavior of mod_perl servers have been discussed in
On 25/06/10 20:00, Rajesh Kumar Mallah wrote:
Dear tom, we have autocommit off in dbi. Any commit or rollback from
the persistent modperl process immediately issues begin work; if the
modperl process is waiting for request the database backend remains in
idle in transaction state. Unless we modif
