[asterisk-bugs] [Asterisk 0018502]: Schema selection support for cel_odbc.conf

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Dec 20 16:18:05 UTC 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18502 
====================================================================== 
Reported By:                pozzalenko
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18502
Category:                   CDR/General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.1.1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-12-20 09:24 CST
Last Modified:              2010-12-20 09:57 CST
====================================================================== 
Summary:                    Schema selection support for cel_odbc.conf
Description: 
*** This issue is exactly the same as
https://issues.asterisk.org/view.php?id=18473 , however, in this case the
file changed is cel_odbc.c ****

We use CEL with an Oracle backend, via ODBC. The CEL table exists inside a
schema (called ASTERISKDBA), and there is a synonym (also called CEL) in
the PUBLIC schema.

When cel_odbc.c calls SQLColumns() to get a list of column names, the
result set contains each column twice --- once for the ASTERISKDBA schema,
and once for the PUBLIC schema. Obviously, this causes INSERTs to error.

This patch adds a "schema" configuration parameter which, when set, passes
the schema name into SQLColumns().

Setting "schema => ASTERISKDBA" (or, for that matter, "schema => PUBLIC")
to cel_odbc.conf fixes this problem in our environment.





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

---------------------------------------------------------------------- 
 (0129798) pozzalenko (reporter) - 2010-12-20 09:57
 https://issues.asterisk.org/view.php?id=18502#c129798 
---------------------------------------------------------------------- 
Okay - I've uploaded it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-20 09:57 pozzalenko     Note Added: 0129798                          
======================================================================




More information about the asterisk-bugs mailing list