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
---------------------------
EDM Wizard doesn't work with PostgreSql columns with domain types
-
- Posts: 7
- Joined: Thu 21 Feb 2008 20:53
-
- Posts: 7
- Joined: Thu 21 Feb 2008 20:53
Another Error
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
---------------------------
---------------------------
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
---------------------------
-
- Posts: 7
- Joined: Thu 21 Feb 2008 20:53
Visual Studio Integration
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.
I have Vista x64, and I imagine setup is not looking in the WOW6432 node or the wrong Program Files directory or something.
-
- Posts: 729
- Joined: Thu 13 Dec 2007 10:24
-
- Posts: 7
- Joined: Thu 21 Feb 2008 20:53
-
- Posts: 729
- Joined: Thu 13 Dec 2007 10:24
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.
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.