Support for SQL Transactions? http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=8930115 2013-05-26T09:09:08Z 2013-05-26T09:09:08Z Marco Menozzi http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8949088 2012-11-30T15:09:50Z 2012-11-30T15:09:50Z

I'm out of office today from 1 p.m to 6 p.m. In case of urgency please leave a message on the mobile phone. Marco

Marco Menozzi 2012-11-30T15:09:50Z Martin Sloan http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8950787 2012-11-30T15:08:32Z 2012-11-30T15:08:32Z

David, Many thanks.  I was curious about this for the reason of taking care with my sql messaging so we're on the same page.  This is all in lab/dev mode.  I didn't know sql statements could be chained so that'll save some overhead, thanks! Marty

Martin Sloan 2012-11-30T15:08:32Z Ludwig Balke http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8943283 2012-11-30T09:27:06Z 2012-11-30T09:27:06Z

I have a problem adding analog devices to a VGx with a security profile having secure mode enabled. Using addGatewaySccpEndpoints results in error "The specified Security Profile is not valid for this device type" Inspired by your post, I tried the follwoing: addPhone with Standard Non-Secure profile do executeUpdateSql with insert into mgcpdevicemember ... update device set fksecurityprofile=... Result: Error 480: The security mode of every real device on any given analog gateway must remain consistent with that of every other device on that gateway... Hence I tried: update device set fksecurityprofile=... insert into mgcpdevicemember ... And now the result: Error 448: The specified Security Profile is not valid for this device type That means, these business rules are implemented as triggers activated by each single action (insert/update). Question: Is there any chance to postpone application of these business rules until the end of transaction? There must be same trick, since manually (GUI) one can add these phones.           

Ludwig Balke 2012-11-30T09:27:06Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8934445 2012-11-30T00:27:22Z 2012-11-30T00:27:22Z

My understanding is that the executeSqlUpdate SQL statement is under-the-covers wrapped in a transaction when executed.  It is possible to include multiple SQL statements in the request (separated by semi-colons), with the effect being a transaction set. Take care with this, as you are updating a mission-critical real-time database - design and testing should be done to ensure that write locks and other DB delays are absolutely minimized.    

David Staudt 2012-11-30T00:27:22Z Martin Sloan http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8930114 2012-11-29T20:53:03Z 2012-11-29T20:53:03Z

Just wondering if anyone knows whether there is support for sql transactions when using the executeSQL methods?   Thanks

Martin Sloan 2012-11-29T20:53:03Z