[asterisk-bugs] [Asterisk 0015953]: [patch] sqlite3 CDRs not working after a reload

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15953 
====================================================================== 
Reported By:                frawd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15953
Category:                   CDR/cdr_sqlite3_custom
Reproducibility:            have not tried
Severity:                   feature
Priority:                   normal
Status:                     ready for review
Asterisk Version:           SVN 
JIRA:                       SWP-222 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-24 08:03 CDT
Last Modified:              2009-10-08 08:47 CDT
====================================================================== 
Summary:                    [patch] sqlite3 CDRs not working after a reload
Description: 
A module reload calls free_config() which sqlite3_closes the db, preventing
CDRs to be logged there until next full restart.

Unfortunately the sqlite3_open is only done on load.

Patch adds a reload option to free_config to prevent it from closing the
sqlite3 db handler. I only tried it on my backport for 1.4, not on trunk.
====================================================================== 

---------------------------------------------------------------------- 
 (0112053) frawd (reporter) - 2009-10-08 08:47
 https://issues.asterisk.org/view.php?id=15953#c112053 
---------------------------------------------------------------------- 
I don't really agree in classifying this bug as a 'feature' by the way, it
is really a bug for us poor sqlite3 users.

Maybe better switching this to 'minor', after all there is a workaround
consisting in stopping and starting asterisk instead of reloading on
configuration change (pain in the A). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-08 08:47 frawd          Note Added: 0112053                          
======================================================================