[asterisk-dev] [Code Review] 3335: [res_config_odbc] Fix for nullable integer columns and keyfield existence check in update_odbc
Matt Jordan
reviewboard at asterisk.org
Fri Mar 14 11:09:59 CDT 2014
> On March 14, 2014, 11:03 a.m., zvision wrote:
> > If I have a similar fix for branch 12, should I upload a diff here or should I create a new review request?
Is the patch the same?
If the patches are the same - minus any syntax changes that would occur during a merge - then the person doing the committing can make the necessary adjustments. If you'd like to leave a patch on the issue as guidance, that's nice.
If there are semantic differences, then it may be worthwhile posting a separate review.
- Matt
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3335/#review11203
-----------------------------------------------------------
On March 14, 2014, 10:29 a.m., zvision wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/3335/
> -----------------------------------------------------------
>
> (Updated March 14, 2014, 10:29 a.m.)
>
>
> Review request for Asterisk Developers.
>
>
> Bugs: ASTERISK-23459
> https://issues.asterisk.org/jira/browse/ASTERISK-23459
>
>
> Repository: Asterisk
>
>
> Description
> -------
>
> This patch fixes setting nullable integer columns to NULL instead of an empty string, which fails for PostgreSQL, for example.
> The current code is supposed to do so, but the check is broken. The patch also allows the first column in the list to be a nullable integer.
> Also, the check for existence of a mandatory column checked for the first column in the list instead of the key field lookup column.
>
>
> Diffs
> -----
>
> http://svn.asterisk.org/svn/asterisk/branches/11/res/res_config_odbc.c 410554
>
> Diff: https://reviewboard.asterisk.org/r/3335/diff/
>
>
> Testing
> -------
>
> Tested by me. Use case scenario: Asterisk + res_odbc + PostgreSQL backend, SIP realtime peers + regs.
> When a 'port' column in SIP regs (I assume this also applies when using sippeers only) is a nullable integer,
> Asterisk tries to write an empty string here during SIP endpoint deregistration.
>
>
> Thanks,
>
> zvision
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20140314/324cd5d7/attachment.html>
More information about the asterisk-dev
mailing list