https://g1r-mp.com/wiki/index.php?action=history&feed=atom&title=DbReconnectDbReconnect - Revision history2026-09-19T14:00:30ZRevision history for this page on the wikiMediaWiki 1.46.0https://g1r-mp.com/wiki/index.php?title=DbReconnect&diff=890&oldid=prevQCherry: Document upcoming 0.1.4 database recovery; organize wiki navigation2026-09-19T10:51:42Z<p>Document upcoming 0.1.4 database recovery; organize wiki navigation</p>
<p><b>New page</b></p><div>= dbReconnect =<br />
'''Available since 0.1.4 (in development; not present in public 0.1.3). Server-side only.'''<br />
<br />
Explicitly requests a fresh session for a disconnected resource-owned MySQL handle, including one fenced after transaction/session loss.<br />
<br />
== Syntax ==<br />
<syntaxhighlight lang="lua"><br />
boolean dbReconnect(DatabaseConnection connection)<br />
</syntaxhighlight><br />
<br />
Returns true if a recovery request was accepted, '''not''' if a connection has already been established. Returns false for foreign/unknown/closed handles, an already connected or reconnecting connection, or one still busy. Observe [[dbGetConnectionState]] or [[onDatabaseConnectionStateChange]] for completion.<br />
<br />
With autoreconnect=false this requests one connection attempt. With autoreconnect=true failed attempts continue with bounded backoff. The original handle is retained and generation increases on success. No failed queries or session SQL are replayed. Calling it for transaction_lost acknowledges session replacement; it cannot resume the transaction or determine whether a lost COMMIT succeeded.<br />
<br />
<syntaxhighlight lang="lua"><br />
local status = dbGetConnectionState(db)<br />
if status and status.state == "disconnected" then<br />
dbReconnect(db) -- asynchronous; check state before submitting more work<br />
end<br />
</syntaxhighlight><br />
<br />
See [[MySQL connection recovery]] for safe transaction handling.<br />
[[Category:Lua Functions]]<br />
[[Category:Server Functions]]<br />
[[Category:Database Functions]]</div>QCherry