Summary: | ASTERISK-17134: [patch] Schema selection support for cel_odbc.conf | ||
Reporter: | Paul Wright (pozzalenko) | Labels: | patch |
Date Opened: | 2010-12-20 09:24:53.000-0600 | Date Closed: | |
Priority: | Major | Regression? | No |
Status: | Open/New | Components: | CDR/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) cel-schema.patch | |
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. ****** ADDITIONAL INFORMATION ****** <inline patch removed by lmadsen> * You can't attach patches inline like that * | ||
Comments: | By: Andrew Latham (lathama) 2010-12-20 09:28:35.000-0600 If you have a license you need to upload the file and tag it. By: Paul Wright (pozzalenko) 2010-12-20 09:57:37.000-0600 Okay - I've uploaded it. |