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

[Asterisk Bug Tracker]

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:                     ready for testing
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-04-09 17:12 CDT
====================================================================== 
Summary:                    [patch] 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','')



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

---------------------------------------------------------------------- 
 (0120242) coolmig (reporter) - 2010-04-09 17:12
 https://issues.asterisk.org/view.php?id=16655#c120242 
---------------------------------------------------------------------- 
I was testing this with 1.6.2.7-rc1, and I found that it works fine, the
query involved (in line 515 of cdr_pgsql.c) is different but takes both the
table and schema into account. So this issue dissappears if you upgrade to
1.6.2.X with no needs of patches like the one I made, it looks like someone
else already did the job on this version.

I tested it works fine with two asterisk instances pointing to a table
named "cdr" on different schemas in the same PostgreSQL database:

asterisk1.cdr
asterisk2.cdr

Records are correctly inserted in the corresponding schema with no errors. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-09 17:12 coolmig        Note Added: 0120242                          
======================================================================