You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove need for $conn->setIsPersistent(true), because there is no sense of “persistence” when HTTP transport used, so errors occur if a close/disconnect can be sent. Same issue may occur with PECL transport because there's no true “connection.”
The text was updated successfully, but these errors were encountered:
alanseiden
changed the title
Ensure HTTP transport does not try to use "persistence"
Ensure HTTP transport does not try to use "persistence" (check if still an issue)
Jul 13, 2016
The purpose of passing a persistence flag into the constructor: To let the toolkit create its own database transport connection and make it a persistent connection.
The persistence flag does not serve any purpose other than telling database connection code whether to make the connection persistent.
I suggest we create a new issue that seeks to look up the persistence value when necessary (see previous bullet point), but no longer passes it around or needing a getter or setter.
Check on this to see if still relevant:
Remove need for $conn->setIsPersistent(true), because there is no sense of “persistence” when HTTP transport used, so errors occur if a close/disconnect can be sent. Same issue may occur with PECL transport because there's no true “connection.”
The text was updated successfully, but these errors were encountered: