[asterisk-bugs] [Asterisk 0012285]: [patch] Permit 'not null' fields to always be set

noreply at bugs.digium.com noreply at bugs.digium.com
Sun Mar 23 22:47:15 CDT 2008


The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12285 
====================================================================== 
Reported By:                Corydon76
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12285
Category:                   CDR/cdr_pgsql
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 110578 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-23-2008 22:47 CDT
Last Modified:              03-23-2008 22:47 CDT
====================================================================== 
Summary:                    [patch] Permit 'not null' fields to always be set
Description: 
Brian Capouch writes, via the -dev list:

I haven't built trunk for a while but tonight I took it up again.

The code builds fine against openWRT, but there seem to be some changes 
to the way that CDR works.  I use Postgres to store CDR records.  I 
can't find mention of the things mentioned below in CHANGES, in any of 
the documentation I could find online, or in the sample configs.

First, it appears that calldate is no longer allowed as a field name in 
the table which will hold the CDR record.  I couldn't get it to work 
unless I set the field name to "start."

There has also been a change in that the fields "accountcode" and 
"userfield" aren't being sent to the backend anymore.  This violates the 
"NOT NULL" constraints on those fields that permeate the documentation 
everywhere online.

I may have missed some critical information along the line, but if not, 
the codebase and existing documentation seem to be out of sync.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-23-08 22:47  Corydon76      SVN Revision (number only!) => 110578          
03-23-08 22:47  Corydon76      Disclaimer on File?       => N/A             
======================================================================




More information about the asterisk-bugs mailing list