S
steve pittman
Guest
sql has cached schema data, including the width of columns for tables that have been used by applications. Even if the ABL updated the sql width of a column, the cached metadata would still contain the old sql width. As Rich explained, we would need new concurrency protocol support to enable sql to learn about a change in sql width. If there were rapid sql width changes, there would be performance implications. hope this helps, .....steve pittman [OE sql architect] On 10/16/2014 11:59 AM, Libor Laubacher wrote: RE: 10.2B08: Option auto adjustment sql-width available? Reply by Libor Laubacher This is a “schema” update, not a particular record update. Or rather this would be. Hypothetically speaking. From: Thomas Mercer-Hursh [ mailto:bounce-tamhas@community.progress.com ] Sent: Thursday, October 16, 2014 5:55 PM To: TU.OE.RDBMS@community.progress.com Subject: RE: [Technical Users - OE RDBMS] 10.2B08: Option auto adjustment sql-width available? RE: 10.2B08: Option auto adjustment sql-width available? Reply by Thomas Mercer-Hursh Still, given that one is simply updating a DB field, the chance of an ABL client doing the update and the SQL client having already started a query that will include the offending record would seem to be extraordinarily small, wouldn't it? Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...