[Asterisk-bugs] [Asterisk 0009279]: fields "start", "answer" and "end" are always empty.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9279 
====================================================================== 
Reported By:                rottenroddy
Assigned To:                junky
====================================================================== 
Project:                    Asterisk
Issue ID:                   9279
Category:                   CDR/cdr_pgsql
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             03-14-2007 13:35 CDT
Last Modified:              07-06-2007 09:06 CDT
====================================================================== 
Summary:                    fields "start", "answer" and "end" are always empty.
Description: 
CDR format and content are different between given interfaces and
documentation is inconsistent. Default CDR construction in cdr-csv is 18
fields and matches the documentation for the module(see below). For the
remaining non-configurable interfaces, mysql,mssql and pgsql, mssql is the
only documentation matching the standard format while the others do not.
mssql was not tested for functionality. cdr_pgsql.so should match the
output of the single standard cdr format for 1.4x. It does not. Fields
"start", "answer" and "end" are always empty.
====================================================================== 

---------------------------------------------------------------------- 
 murf - 07-06-07 09:06  
---------------------------------------------------------------------- 
Juggie-- your license is approved!!! Yay!! (Sorry for the delay...)

I've looked at your patch, and have but just one question: What will
happen to all those using pgsql at this point in time? Their billdate
column will no longer be populated, and the backend will try to write to 3
new fields that don't exist.

It looks like pgsql users will have to update their table schema, and
maybe, maybe tweek their post-processing software to handle at least the
changed field name.

As such, this change in behavior probably won't be allowed in 1.4, but we
can add it to trunk.

Does pgsql have an ODBC interface available? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-06-07 09:06  murf           Note Added: 0066584                          
======================================================================