Some ODBC drivers don't set the CHAR_OCTET_LENGTH field correctly.
authorTilghman Lesher <tilghman@meg.abyt.es>
Fri, 27 Jul 2007 23:21:23 +0000 (23:21 +0000)
committerTilghman Lesher <tilghman@meg.abyt.es>
Fri, 27 Jul 2007 23:21:23 +0000 (23:21 +0000)
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@77603 65c4cc65-6c06-0410-ace0-fbb531ad65f3

cdr/cdr_adaptive_odbc.c

index 8c3b1e5..12e9820 100644 (file)
@@ -198,6 +198,13 @@ static int load_config(void)
                        SQLGetData(stmt, 11, SQL_C_SHORT, &entry->nullable, sizeof(entry->nullable), NULL);
                        SQLGetData(stmt, 16, SQL_C_LONG, &entry->octetlen, sizeof(entry->octetlen), NULL);
 
+                       /* Specification states that the octenlen should be the maximum number of bytes
+                        * returned in a char or binary column, but it seems that some drivers just set
+                        * it to NULL. (Bad Postgres! No biscuit!) */
+                       if (entry->octetlen == 0)
+                               entry->octetlen = entry->size;
+
+                       ast_verb(10, "Found %s column with type %hd with len %ld, octetlen %ld, and numlen (%hd,%hd)\n", entry->name, entry->type, entry->size, entry->octetlen, entry->decimals, entry->radix);
                        /* Insert column info into column list */
                        AST_LIST_INSERT_TAIL(&(tableptr->columns), entry, list);
                        res = 0;