[asterisk-bugs] [Asterisk 0015663]: CDR dynamic fields in postgresql

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=15663 
====================================================================== 
Reported By:                geraldoclezio
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15663
Category:                   CDR/cdr_pgsql
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-08-05 15:28 CDT
Last Modified:              2009-08-06 09:00 CDT
====================================================================== 
Summary:                    CDR dynamic fields in postgresql
Description: 
The bug 0009279 to be placed as resolved version 1.4.X but the test the
patch "20080125__bug9279.diff.txt" does not work.

Is there a viable solution to cdr_pgsql accept dynamic fields?
====================================================================== 

---------------------------------------------------------------------- 
 (0108702) tilghman (administrator) - 2009-08-06 09:00
 https://issues.asterisk.org/view.php?id=15663#c108702 
---------------------------------------------------------------------- 
Only in 1.6.x.  We don't support adding new features to 1.4 (or any other
released branch).  If you want dynamic CDR fields, there is a backport of
cdr_adaptive_odbc in SVN at
http://svncommunity.digium.com/svn/tilghman/branches/1.4 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-06 09:00 tilghman       Note Added: 0108702                          
2009-08-06 09:00 tilghman       Status                   new => closed       
2009-08-06 09:00 tilghman       Resolution               open => no change
required
======================================================================