[asterisk-bugs] [Asterisk 0012107]: variable data truncated when attempting password changes using odbc backed

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12107 
====================================================================== 
Reported By:                asgaroth
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12107
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-29-2008 05:34 CST
Last Modified:              02-29-2008 05:38 CST
====================================================================== 
Summary:                    variable data truncated when attempting password
changes using odbc backed
Description: 
Our uniqid field for our voicemail accounts is a 36 character variable
field which is a generated guid. What appears to be happening is that when
the update to the voicemailaccounts table is run, to update the password,
only half of this guid is passed into the query, ie, only 18 characters of
the 36 character uniqid is passed in the update query.

For example:

UPDATE voicemailaccounts SET password='56789' WHERE
uniqueid='fcdadd0c-a2b3-4e77-'

in this case uniqueid is supposed to be:

'fcdadd0c-a2b3-4e77-88d0-e2d37ab185f2' 

The asterisk console does not report any errors and Alison says that the
password has been successfully changed. 

However, the password is unchanged as the update query mentioned above
would not have found a record to update.
====================================================================== 

---------------------------------------------------------------------- 
 asgaroth - 02-29-08 05:38  
---------------------------------------------------------------------- 
I have uploaded the unixODBC trace.log, and the pgsqlODBC driver
communication log and debug log to help try and get to the bottom of this
issue. If you require any additional information, please dont hesitate to
ask.

This particular issue is a show stopper for us in migration to odbc
voicemail storage. I cannot see anything obvious wrong with the ODBC driver
as it is working well otherwise. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-29-08 05:38  asgaroth       Note Added: 0083145                          
======================================================================