Suggestion for better debug

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
baba
Posts: 22
Joined: Thu 14 Apr 2005 16:40

Suggestion for better debug

Post by baba » Fri 08 Jul 2011 20:49

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.

Shalex
Site Admin
Posts: 8241
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Wed 13 Jul 2011 12:27

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).

Shalex
Site Admin
Posts: 8241
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Wed 20 Jul 2011 11:20

The internal threads created by provider will be named in a user-friendly way starting from the next build of dotConnect for PostgreSQL. We will post here when the corresponding build is available for download.

Shalex
Site Admin
Posts: 8241
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Fri 29 Jul 2011 08:12

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 .

baba
Posts: 22
Joined: Thu 14 Apr 2005 16:40

About visible variables....

Post by baba » Wed 03 Aug 2011 14:58

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

baba
Posts: 22
Joined: Thu 14 Apr 2005 16:40

Post by baba » Wed 03 Aug 2011 15:01

Ho, i forgat... g is just an example.

Lot of other letters makes the same trouble.
I think they should be marked internal or protected...

Seb

Shalex
Site Admin
Posts: 8241
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Thu 04 Aug 2011 13:56

baba wrote:'Devart.Data.PostgreSql.g' is inaccessible due to its protection level
"Devart.Data.PostgreSql.g" is the name of obfuscated class in the Devart.Data.PostgreSql.dll assembly. It is marked as "internal".
Other letters are also the names of obfuscated internal classes/enumerations.

Post Reply