Page 1 of 1

Generate database from model.

Posted: Mon 08 Mar 2010 04:59
by prasongt
i use build 5.60 Beta and got an error when i try to generate database from model.

After the connection was set, the wizard try to retrieve object from database. Error occur here "Object reference not set to ans instance of an object".

Could anyone tell me how to handle this?

Thank you,

Posted: Tue 09 Mar 2010 10:20
by AndreyR
Thank you for the report, we have reproduced the error.
I will let you know about the results of our investigation.

Posted: Tue 09 Mar 2010 11:03
by prasongt
so if we buy your product now (Developer edition, Site License), will we get an upgrade when you release the complete product ?

right now we are starting new project that requires an Oracle provider for EF4.

if possible, can you provide your release (or fix) schedule for this issue (generate DB from model)?

Posted: Wed 10 Mar 2010 15:18
by AndreyR
If you purchase dotConnect, you get a year subscription on the new builds.
As for the timeframe, we plan to release a new build this month.

Posted: Thu 11 Mar 2010 04:17
by prasongt
Can you confirm that this issue will be solved in the next release this month?
Because I have a plan to start implement within 1-2 weeks.

Posted: Thu 11 Mar 2010 14:11
by AndreyR
Yes, we have already fixed the problem.
Anyway, there is a workaround.
You can manually set the MaxLength facet for the conceptual String properties in the model. This should be enough to overcome the probelm.

Posted: Sat 13 Mar 2010 05:32
by prasongt
Thank you for the solution. I've try the workaround. It works well without any error but the script generated is for SQL not Oracle Database.

Have i did something wrong? Does the product support this feature?

Posted: Mon 15 Mar 2010 09:14
by AndreyR
Please make sure that you have chosen the Devart SSDLToOracle.tt (VS) DDL Generation Template in the model properties.

Posted: Tue 16 Mar 2010 04:32
by prasongt
Thanks AndreyR. The problem is solved. :D

Posted: Mon 29 Mar 2010 06:39
by AndreyR
We have fixed this problem. Look forward to the nearest build.