"Race condition" while trying to "map" Postgres db in VS2010
"Race condition" while trying to "map" Postgres db in VS2010
Hi!
We're currently evaluating dotConnect for PostgreSQL as a possible data-provider in a fortcoming project. We downloaded the 4.95 version and installed. However we immediately ran into a complete stop when we tried to create an "entity framework class". We successfully completed the data-provider steps up to the point when we should select which tables to map. After clicking "Finish" we ended up in a "race condition" where the cores of the CPU were utilized 100%. The only way to stop this condition was to force VS2010 to shutdown.
We also tried another scenario where we only selected one table in the database - a table with NO relations whatsoever. We ended up with the same result. The database we use for testing is small: only 30+ tables. FYI - we tried to "map" the "postgis" db which is installed as part of the GIS stuff and that worked without a glitch.
The enviroment we're running this under is:
Intel Core Duo 2.33GHz
4 Gb RAM
WinXP 32-bit SP3
VS2010 Professional
PostgreSQL v8.4
Any ides what could be wrong?
Thanks in advance!
/Peter
We're currently evaluating dotConnect for PostgreSQL as a possible data-provider in a fortcoming project. We downloaded the 4.95 version and installed. However we immediately ran into a complete stop when we tried to create an "entity framework class". We successfully completed the data-provider steps up to the point when we should select which tables to map. After clicking "Finish" we ended up in a "race condition" where the cores of the CPU were utilized 100%. The only way to stop this condition was to force VS2010 to shutdown.
We also tried another scenario where we only selected one table in the database - a table with NO relations whatsoever. We ended up with the same result. The database we use for testing is small: only 30+ tables. FYI - we tried to "map" the "postgis" db which is installed as part of the GIS stuff and that worked without a glitch.
The enviroment we're running this under is:
Intel Core Duo 2.33GHz
4 Gb RAM
WinXP 32-bit SP3
VS2010 Professional
PostgreSQL v8.4
Any ides what could be wrong?
Thanks in advance!
/Peter
Could you please try the 5.0 Beta version of dotConnect for PostgreSQL?
We have made a number of fixes associated with model generation performance in it.
I have made a couple of tests (using both Devart Entity model and Microsoft Entity model) and succeeded in adding tables with geometry columns.
Please notify us if the problem persists at your side.
We have made a number of fixes associated with model generation performance in it.
I have made a couple of tests (using both Devart Entity model and Microsoft Entity model) and succeeded in adding tables with geometry columns.
Please notify us if the problem persists at your side.
"Race condition" - tried v5.0 beta
Hi!AndreyR wrote:Could you please try the 5.0 Beta version of dotConnect for PostgreSQL?
We have made a number of fixes associated with model generation performance in it.
I have made a couple of tests (using both Devart Entity model and Microsoft Entity model) and succeeded in adding tables with geometry columns.
Please notify us if the problem persists at your side.
We tried v5 beta but the problem persists! What information can we provide to help you investigate this further?
Kind regards
/Peter
Devart Entity Model tested
Hi!
Some progress!
If we used the "Devart Entity Model" we managed to "map" the underlying datamodel in VS2010! However - when we tried to expose the entity model using .Net 4 WCF Data Services we get a
Inconsistent accessibility: base class
'System.Data.Services.DataService'
is less accessible than class 'Our DataService...
At least some progress! What could be wrong with our DataService declaration?
Cheers
/Peter
Some progress!
If we used the "Devart Entity Model" we managed to "map" the underlying datamodel in VS2010! However - when we tried to expose the entity model using .Net 4 WCF Data Services we get a
Inconsistent accessibility: base class
'System.Data.Services.DataService'
is less accessible than class 'Our DataService...
At least some progress! What could be wrong with our DataService declaration?
Cheers
/Peter
Partial -> public made the project compile but...
Hi again!
We changed the declaration of our "entity class" from partial to public, and then we managed to compile our WCF Data Service project! However, we immediately ran into another problem:
Trying to publish *any* of the tables/classes in the underlying datamodel failed...
config.SetEntitySetAccessRule("", EntitySetRights.All);
Where EntityName = {* | entityname}
Iow - publishing *any* of the tables failed. Furthermore adding a service operation also failed.
Cheers,
/Peter
We changed the declaration of our "entity class" from partial to public, and then we managed to compile our WCF Data Service project! However, we immediately ran into another problem:
Trying to publish *any* of the tables/classes in the underlying datamodel failed...
config.SetEntitySetAccessRule("", EntitySetRights.All);
Where EntityName = {* | entityname}
Iow - publishing *any* of the tables failed. Furthermore adding a service operation also failed.
Cheers,
/Peter
PostgreSQL version
Postgres server is 8.4.3.1 running under Windows XP 32-bit SP3