Hello,
We are debugging a heavy application using your dotnet postgresql driver and many threads.
We could appreciate two improvements:
1) Could you name your threads so we could identify them when using Intellitrace or any simpler thread debugger. At the very start of our thread we use something like :
Thread.CurrentThread.Name = "Devart_PgSql_" + Name; where name is whatever you like. Working with only the ID is really a pain.
2) Could you protect all unnecessary variables. You have lots of variables beeing nemad with only one letter. I do not not think we need to see them. And in case of mis-coding, the compiler silently link to your variables. "protected" or "internal" could be relevant.
Thanks.
Suggestion for better debug
1. We will investigate the possibility of renaming the threads we create in our code (with asynchronous queries, etc) and notify you about the results.
2. Please tell us which our public interface being named with only one letter. Also specify your current version (x.xx.xxx) of dotConnect for PostgreSQL. If you mean our local variable, they are obfuscated during a build process (it is OK).
2. Please tell us which our public interface being named with only one letter. Also specify your current version (x.xx.xxx) of dotConnect for PostgreSQL. If you mean our local variable, they are obfuscated during a build process (it is OK).
New build of dotConnect for PostgreSQL 5.30.196 is available for download!
It can be downloaded from http://www.devart.com/dotconnect/postgr ... nload.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ .
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=21607 .
It can be downloaded from http://www.devart.com/dotconnect/postgr ... nload.html (trial version) or from Registered Users' Area (for users with valid subscription only): http://secure.devart.com/ .
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=21607 .
About visible variables....
Just to do the test, try:
using Devart.Data.Postgresql;
// g does not exist in my context.
......
if(g==12)
g=13;
......
You get:
Error 3 'Devart.Data.PostgreSql.g' is inaccessible due to its protection level F:\projects\testsuite\testsuite\acltester.cs 65 24 testsuite
Error 5 'Devart.Data.PostgreSql.g' is inaccessible due to its protection level F:\projects\testsuite\testsuite\acltester.cs 66 17 testsuite
Error 2 'Devart.Data.PostgreSql.g' is a 'type' but is used like a 'variable' F:\projects\testsuite\testsuite\acltester.cs 65 24 testsuite
Error 4 'Devart.Data.PostgreSql.g' is a 'type' but is used like a 'variable' F:\projects\testsuite\testsuite\acltester.cs 66 17 testsuite
using Devart.Data.Postgresql;
// g does not exist in my context.
......
if(g==12)
g=13;
......
You get:
Error 3 'Devart.Data.PostgreSql.g' is inaccessible due to its protection level F:\projects\testsuite\testsuite\acltester.cs 65 24 testsuite
Error 5 'Devart.Data.PostgreSql.g' is inaccessible due to its protection level F:\projects\testsuite\testsuite\acltester.cs 66 17 testsuite
Error 2 'Devart.Data.PostgreSql.g' is a 'type' but is used like a 'variable' F:\projects\testsuite\testsuite\acltester.cs 65 24 testsuite
Error 4 'Devart.Data.PostgreSql.g' is a 'type' but is used like a 'variable' F:\projects\testsuite\testsuite\acltester.cs 66 17 testsuite