[asterisk-bugs] [Asterisk 0016655]: Double fields in SQL query

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Mar 16 12:20:02 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16655 
====================================================================== 
Reported By:                Yarik_rad
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16655
Category:                   CDR/cdr_pgsql
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0.21 
JIRA:                       SWP-780 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-01-20 04:48 CST
Last Modified:              2010-03-16 12:20 CDT
====================================================================== 
Summary:                    Double fields in SQL query
Description: 
Try to connect Asterisk server with PostgreSQl database I've double fields
in SQL quere send to datbase.

Here is log of database server:

COMMAND:  INSERT INTO cdr
("calldate","clid","src","dst","dcontext","channel","dstchannel","lastapp","lastdata","duration","billsec","disposition","amaflags",
"uniqueid","calldate","clid","src","dst","dcontext","channel","dstchannel","lastapp","lastdata","duration","billsec","disposition","amaflags","uniqueid","calldate",
"clid","src","dst","dcontext","channel","dstchannel","lastapp","lastdata","duration","billsec","disposition","amaflags","accountcode","uniqueid","userfield",
"calldate","clid","src","dst","dcontext","channel","dstchannel","lastapp","lastdata","duration","billsec","disposition","amaflags","accountcode","uniqueid","userfield")
VALUES ('2010-01-20 13:43:16','"User714"
<714>','714','9060','kvartira','SIP/714-00000057','SIP/pstn-00000058','Dial','SIP/999060 at pstn',13,2,'ANSWERED',3,'1263984196.87',
'2010-01-20 13:43:16','"User714"
<714>','714','9060','kvartira','SIP/714-00000057','SIP/pstn-00000058','Dial','SIP/999060 at pstn',13,2,'ANSWERED',3,'1263984196.87',
'2010-01-20 13:43:16','"User714"
<714>','714','9060','kvartira','SIP/714-00000057','SIP/pstn-00000058','Dial','SIP/999060 at pstn',13,2,'ANSWERED',3,'','1263984196.87','',
'2010-01-20 13:43:16','"User714"
<714>','714','9060','kvartira','SIP/714-00000057','SIP/pstn-00000058','Dial','SIP/999060 at pstn',13,2,'ANSWERED',3,'','1263984196.87','')



====================================================================== 

---------------------------------------------------------------------- 
 (0119441) coolmig (reporter) - 2010-03-16 12:20
 https://issues.asterisk.org/view.php?id=16655#c119441 
---------------------------------------------------------------------- 
Found the cause, I have two different schemas with the table cdr (same
name). The query that brings the columns is this one, according to
cdr_pgsql.c source code:

select a.attname, t.typname, a.attlen, a.attnotnull, d.adsrc from pg_class
c, pg_type t, pg_attribute a left outer join pg_attrdef d on a.atthasdef
and d.adrelid = a.attrelid and d.adnum = a.attnum where c.oid = a.attrelid
and a.atttypid = t.oid and (a.attnum > 0) and c.relname = 'cdr' order by
c.relname, attnum;

If I change the name of the table on the other schema, the fields are
brought ok.

One workaround is to have different names for the CDR table, the solution
would be fixing the query to seek only in the schema where we have
permission... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-16 12:20 coolmig        Note Added: 0119441                          
======================================================================




More information about the asterisk-bugs mailing list