Philippe Chal�at wrote >Hello,
>We are using SapDb 7.4 in production for critical applications. That's >fine. The kernel is robust and efficient enough for our needs. >Developpers are very responsive (for example for a problem we had with >BigDecimal). But... >We discovered recently that even with isolation level 1, "Read >commited", not committed deleted rows, are also deleted for other >transaction... We never tested that, as far as the doc for isolation >level 1 says clearly : >"When rows are inserted, updated or deleted, implicit exclusive locks >are assigned to the transaction for the rows concerned. These cannot be >released until the end of the transaction." >I read some interesting thread on this >(http://archives.neohapsis.com/archives/dev/sapdb/2003-q2/0348.html) and >I would like to know if some evolution is planned on this point. Thanks >in advance. We have no chance to solve this problem in the near future. Of course we know this may be a serious problem. We therefore will change the behavior in the future, but this is at least a medium term item. Best Regards, Thomas -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
