Another typo fix and comment... Open Connection Open Connection Open Connection Close Connection Close Connection Close Connection
Without some sort of identifier on the log messages you don't know which Close Connections match to which Open Connections. It would be better if some sort of identifier (a simple incrementing int) was attached to the message: Open Connection 1 Open Connection 2 Open Connection 3 Close Connection 2 Close Connection 1 Close Connection 3 I think IBatisNet should mirror the way Java does it as far as the wording and layout of the log messages. --- "Ron Grabowski (JIRA)" <ibatis-dev@incubator.apache.org> wrote: > [ > http://issues.apache.org/jira/browse/IBATISNET-35?page=comments#action_62696 > ] > > Ron Grabowski commented on IBATISNET-35: > ---------------------------------------- > > During a chat with Larry Meadors on the #ibatis chat room I learned > that the numbers present in some debug statements: > > {conn-100000} Connection > > do not really mean anything (the leading 1000 part at least). They > are just a way to group related items. Perhaps we could use > GetHashCode() or some sort of CRC32 based on the connection string to > uniquely identify connections. In the current version of IBatis there > isn't any way to distinguish connections from each other. If a system > is making calls to a to an Access database and a SQL Server database, > the log files just report that a connection has been opened. Another > example of why the connection logged needs to have some identifier > with it would be if you did this: > > 1 - open connection to access database > 2 - open connection to sql server database > 3 - open connection to sql server database > > 2 - closed connection to sql server database > 1 - closed connection to access datbase > 3 - closed connection to sql server database > > Currently, the log files would displaying something along the lines > of: > > Open Connection > Open Connectin > Close Connection > Close Connection > Close Connection
