Chris Gamache wrote:
>
> That is my point exactly. That is why (windows?) connection
> pooling breaks this model. It wouldn't be a problem if there
> were a way to undefine currval() for all sequences...
> It would be a command issued by the ODBC driver when the
> connection is made (best), or by the connecting process as
> its first order of business (do-able).
How could the driver know if the connection is recycled ?
SQL..Connect API function isn't called when the connection
is recycled.
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/