Reworked the part of the ConnectionPool unit test that ensures that connections expire when they get too old: the test assumed that the implementation of ::operator new() doesn't reuse pointers when you allocate an object, deallocate it, and then allocate an object of the exact same type.  On RHEL3, at least, this does happen, and rightfully so; why not re-use the space made in the heap by the previous allocation?  We now test for object uniqueness in a more robust way.
Reworked the part of the ConnectionPool unit test that ensures that
connections expire when they get too old: the test assumed that the
implementation of ::operator new() doesn't reuse pointers when you
allocate an object, deallocate it, and then allocate an object of the
exact same type.  On RHEL3, at least, this does happen, and rightfully
so; why not re-use the space made in the heap by the previous
allocation?  We now test for object uniqueness in a more robust way.


git-svn-id: 1a57124bbb9aca193a920d0ffd753d488afb922b@2225 5946f024-35f4-0310-b1b3-9a3be3380cfb

veprbl/mysqlpp,veprbl/mysqlpp,veprbl/mysqlpp