EntityDeveloper bugs

Alladin · Post by **Alladin** » Fri 04 Feb 2011 13:40

1) State of expanded/collapsed navigation properties is not saved. Monkey job is to expand all of them before printing.

2) Associations lines get messed up after reopening.

3) Page layout is not visible - some kind of visual cue would be nice. One has to print several times until the print model fits paper more or less pretty.

Example of paper waste

AndreyR · Post by **AndreyR** » Fri 04 Feb 2011 15:27

Thank you for the inquiry, we will investigate the possibility of changing this behaviour.
I will post here about the results of our investigation.

Alladin · Post by **Alladin** » Fri 04 Feb 2011 18:04

4) In my model PK property declared with Server Data Type = RAW(16) NOT NULL DEFAULT SYS_GUID(), however Entity Developer generates DB script without "default" part.

Alladin · Post by **Alladin** » Sun 06 Feb 2011 13:51

5) In Oracle EF4 model mode, generated script is CASE-SENSITIVE!!! Tables names, column names all are in quotes (o, boy!)....

Alladin · Post by **Alladin** » Sun 06 Feb 2011 13:58

6) In generated database upgrade script window, button COPY TO CLIPBOARD does NOT work.

AndreyR · Post by **AndreyR** » Tue 08 Feb 2011 13:18

You can see the page layout: right-click the designer surface and set the Show Print Markup option.
The Copy to clipboard button copies only the selection.
The Server Data Type property ignores the Default value setting. You can try setting the Default value in the Properties window of your PK in Model Explorer. However, SYS_GUID() is currently not supported, we are investigating the situation.
Concerning case sensitivity: we generate the script using the Storage columns and tables. If they are named in uppercase, no quoting is performed, in other case there will be quotes to provide the correct case. You can set the desired case for database objects in the Database Mapping dialog (Model Settings->Synchronization).

seser · Post by **seser** » Sat 12 Feb 2011 10:03

in "Methods Properties" "Return type" list is not sorted.

AndreyR · Post by **AndreyR** » Mon 14 Feb 2011 13:51

seser, thank you for the inquiry. We will investigate the possibility to change this behaviour.
I will post here about the results of our investigation.

AndreyR · Post by **AndreyR** » Mon 21 Feb 2011 16:26

We have added sorting for the method's Return Type combo box.

AndreyR · Post by **AndreyR** » Thu 24 Feb 2011 15:12

We have released a new 3.20.89 build of Entity Developer today.
This build provides sorting in the method's Return Type combo box.
It is available for download here.
If you need Entity Developer for dotConnect, please download the latest build of the corresponding dotConnect.
If you are a registered user, you can get the non-Trial edition from Registered Users' Area.
Detailed information about this build is available here.

Alladin · Post by **Alladin** » Fri 04 Mar 2011 15:29

Default values for RAW(16), DATE and TIMESTAMP columns in database model do not allow standard Oracle functions as DEFAULT values.

For example, SYS_GUID(), SYSTIMESTAMP, SYSDATE...

StanislavK · Post by **StanislavK** » Mon 07 Mar 2011 15:11

The point is that the 'Default Value' setting of entity properties is parsed to the type of this property as a string. As, for example, 'sysdate' or 'DateTime.Now' literals cannot be parsed by the DateTime structure, they shouldn't be used as default values.

To implement the behaviour you are speaking about, you can, for example, create the default entity constructor that sets the needed properties to, e.g., DateTime.Now or Guid.NewGuid().

Alladin · Post by **Alladin** » Mon 07 Mar 2011 15:21

The point is that the 'Default Value' is part of the generated DB Schema script, which has to be manually corrected to contain all those default values. And since the DB schema usually used not only by EF client, but also other clients, all those default should be in DB model rather than in EF model. Of course, if they are also mirrored in EF model, it is also ok.

And in case of string literal constants it works, what's a big deal to implement certain set of built-in server functions? every DB has sys_guid() function or its analogue, every DB has sysdate and systimestamp...

C'mon guys

AndreyR · Post by **AndreyR** » Thu 10 Mar 2011 16:56

Thank you for the suggestion.
We will investigate the possibility of implementing this feature, but we don't have any definite timeframe for it.