You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adriano, is it tested anyhow / anyway except SAS? I do not see any code problems at the first glance, but agree that we are trying to walk on a very thin ice at beta stage.
Next, I see at least one potential problem with this improvement - it makes possible to have bad programming style. Imagine MT application, which is using single attachment in all threads. With this improvement it will be very hard to notice any problem as long as such application is not running on SMP system under high load. And I can imagine a ticket like 'FB 2.5 badly supports SMP in MT environment'.
Alex, I somewhat disagree. Surely we should clearly document that we don't support concurrent access to an attachment, regardless of whether we block or throw an error. As soon as it's documented, everybody stepping on this rake can be reasonably blamed in the support lists or the tracker. I'm not sure we can (or even should try to) protect from whatever stupid application users can code.
Submitted by: @asfernandes
It was throwing "attachment handle is busy" error. Now callers will block until others requests are completed.
Commits: 2d8d9dd
The text was updated successfully, but these errors were encountered: