EDM Wizard doesn't work with PostgreSql columns with domain types

EDM Wizard doesn't work with PostgreSql columns with domain types

Postby jmouch-corelab@ssgx.com » Thu 21 Feb 2008 21:01

I cannot get the EDM Wizard to work with PostgreSql custom types.

I have a few custom types defined in my schema. For example, d_enabled is basically a boolean.

When I run the wizard on this schema, I get an error for each column with a non-standard type.

I also get a couple different errors that I can't make heads or tails of.

Here is the output of the error dialog:



---------------------------
Error
---------------------------
Value cannot be null.

Parameter name: storeEntityContainer



Generator warnings:

Error Code: 6005

Severity: Warning

Message: The data type 'd_enabled' is not supported, the column 'enabled' in table 'c_customer.account' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_create_time' is not supported, the column 'create_time' in table 'c_customer.account' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_update_time' is not supported, the column 'update_time' in table 'c_customer.account' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_create_time' is not supported, the column 'create_time' in table 'c_customer.attribute' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_update_time' is not supported, the column 'update_time' in table 'c_customer.attribute' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_create_time' is not supported, the column 'create_time' in table 'c_customer.attribute_default' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_update_time' is not supported, the column 'update_time' in table 'c_customer.attribute_default' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_create_time' is not supported, the column 'create_time' in table 'c_customer.attribute_type' was excluded.



Error Code: 6005

Severity: Warning

Message: The data type 'd_update_time' is not supported, the column 'update_time' in table 'c_customer.attribute_type' was excluded.



Error Code: 6003

Severity: Error

Message: The given key was not present in the dictionary.




---------------------------
OK
---------------------------
jmouch-corelab@ssgx.com
 
Posts: 7
Joined: Thu 21 Feb 2008 20:53

Another Error

Postby jmouch-corelab@ssgx.com » Thu 21 Feb 2008 23:06

Here is another error I can get:

---------------------------
Error
---------------------------
Value cannot be null.

Parameter name: storeEntityContainer



Generator warnings:

Error Code: 6003

Severity: Error

Message: The given key was not present in the dictionary.




---------------------------
OK
---------------------------
jmouch-corelab@ssgx.com
 
Posts: 7
Joined: Thu 21 Feb 2008 20:53

Visual Studio Integration

Postby jmouch-corelab@ssgx.com » Thu 21 Feb 2008 23:08

Also, are you supposed to be able to get to this wizard from Visual Studio? If so, then I do not have that option, and I'd guess it's because of an error I got during setup that said it could not find devenv.exe using the registry.

I have Vista x64, and I imagine setup is not looking in the WOW6432 node or the wrong Program Files directory or something.
jmouch-corelab@ssgx.com
 
Posts: 7
Joined: Thu 21 Feb 2008 20:53

Postby Alexey.mdr » Fri 22 Feb 2008 08:28

PostgreSQLDirect .NET EDM wizard is a standalone application.
Please send me (alexeyman*crlab*com) your table definitions.
We will investigate this issue.
Alexey.mdr
 
Posts: 729
Joined: Thu 13 Dec 2007 10:24

Postby jmouch-corelab@ssgx.com » Fri 22 Feb 2008 14:26

I'm afraid I can't send our database schema, as my employer wouldn't be too happy. :)

So you're saying that you don't have any problems with custom types?
jmouch-corelab@ssgx.com
 
Posts: 7
Joined: Thu 21 Feb 2008 20:53

Postby Alexey.mdr » Fri 22 Feb 2008 18:00

Sometimes we do have bugs. It's natural.
That's why I'm asking you for a peace of code to reproduce the error.
Probably you will manage to allocate the problem place.
Say, if you send a small table definition, where the error constantly reproduces.
I suggest, your employer won't be against it, as you are not showing program logic or anything.
And we'll be far more happy to fix the bug.
Moreover, you will continue working without searching for tricks to overcome the bug.
Alexey.mdr
 
Posts: 729
Joined: Thu 13 Dec 2007 10:24


Return to dotConnect for PostgreSQL