From: HERNAN M. F. <her...@ob...> - 2013-07-02 16:45:40
|
Hi, Profiling my application I found that one bottleneck seems to be when canceling a cursor. It also happens even if it was already consumed (i.e., finished to read all the rows). Is this an expected behavior? I'm asking because it may very well be a bug in our data layers. I might also avoid the command.Cancel() call when a cursor is consumed if that is better practice. My platform: .NET 4.0 FirebirdClient 3.0.2.0 Firebird Server 2.5.1.26531 (embedded) If it helps, the profiler marks the methods BuildSqlState() and BuildExceptionMessage() from FirebirdSql.Data.Common.IscException. Regards, Hernán Martínez-Foffani |