BIND 10 #1444: DATASRC_SQLITE_DROPCONN log message not useful

[BIND 10 Development]

#1444: DATASRC_SQLITE_DROPCONN log message not useful
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:  major  |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [ticket:1444 jreed]:
 > I had this log message:
 >
 > {{{
 >
 >  DATASRC_SQLITE_DROPCONN SQLite3Database is being deinitialized
 >
 >            The object around a database connection is being destroyed.
 >
 > }}}
 >
 > But reading the log description doesn't help me.
 >
 > Jelte said "it can't say more than 'because the destructor has been
 called'; in that sense, that log message is pretty much useless."

 I don't necessarily think it's a problem.  After all, this is a
 "trace" level debug log, so it could be reasonably possible that a
 single log message in itself may not be so informative (nor is its
 "detailed" description).

 But we may be able to improve the main log message a bit by including
 the DB name (in this case the SQLite3 database file).

-- 
Ticket URL: <http://bind10.isc.org/ticket/1444#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development