Hi Noah,
> Would you like to propose a patch?
Sure. I will work on creating a document patch.
However, I found another problem while testing to make sure that the use cases were valid.
> - Each thread does its own CONNECT, DISCONNECT, and other commands.
> Each thread has its own default connection. No sharing at all."
In that case, if I execute CONNECT with same connection-string on each threads without connection-name, the later
CONNECTwas skipped.
Then, ECPGdebug shows following message.
ECPGconnect: connection identifier (null) is already in use
This seems to indicate that CONNECT need to specify connection-name even if we use the default connection in each
thread.
This also seems to me to be an undesirable behavior in multiple thread.
Or do we need to name all connections if we use multiple connections, even in multiple thread?
Regards,
Yusuke Egashira
