OpenAccess first time in oracle

[Juan Angel]

I tested OpenAccess ORM 2010.2.714 with oracle 9i and this is my suggesttions:

REVERSE MAPPING:
- In large databases (in my case 900 tables and 150 views) when you "Update From Database", it's necessary a box to filter tables (maybe similiar that Model Schema Explorer) and views and maybe an any way for show/no show tables, views, strored procedures and please GROUP BY schemas, my user database use 3 oracle schemas, but use default schema almost always. To minimize load first load time, load ONLY default schema. I prefer this order: tables, views, and strored procedures. Views and strored procedures can appear collapsed.
- Add a table from database and add to model, OK. Tomorrow add a new field to table in database. Remove table from model, but it's impossible delete this entity or update from database: don`t appear if it was added. I need edit xml add remove manually this entity and "Update from Database" again.
- In all OpenAccess interface, and particulary in Model Schema Name, i prefer that all entities (tables, views, strored procedures, etc) group by schemas and order alphabetically, but field of entities (fields of tables, field of views) appear in creation/database order.

FORWARD MAPPING:
- Datatype "DateTime" don't exist in oracle, only exist "Date", however the script generated "DateTime", obviously script don`t run.
- I don´t know how create relationship between entities (foreignkeys between tables). I try "Association" tool from toolbox, but don´t run.
- I believe that "Add New Table" window need more interface power/productivity. For example: Copy and Paste columns, reorder columns. Also copy and Paste tables are a good idea.

GENERAL
I love SQLServer (identity fields, database diagrams designer, easy to manage, easy VS integration), but my company requiriments says ONLY ORACLE, if OpenAccess can provide in ORACLE:
- Identity fields (in oracle can simulate with sequences)
- Bool DataType field
- A similar interface of database diagrams designer (forward mapping): copy and paste fields, create foreignkeys with drag and drop, change and create primarykeys, etc with forward mapping.

With Identity fields and powerfull database diagrams designer and the actual ORM features, OpenAccess would be the most powerfull tool for oracle developers.

[Zoran]

Hi Juan Angel,

Thank you for writing.
We will definitely be working on the experience with big databases, and not only with the Update from database wizard but with the visual designer as a whole.

I am not sure that I completely understand the issue that you mention where you were not seeing a table in the Update from database wizard and had to edit the xml. Specifically this paragraph from your post:

"Add a table from database and add to model, OK. Tomorrow add a new field to table in database. Remove table from model, but it's impossible delete this entity or update from database: don`t appear if it was added. I need edit xml add remove manually this entity and "Update from Database" again."

Can you please give us more information about that case? What do you mean by "remove table from model"? Why did you need to do it? What steps did you try in order to do it?

Usually when you add a column to a table in the database, when you run the Update from database wizard you will be presented with a change set item that shows the added column. Didn't that work for you?

The "DateTime" instead of "Date" issue has been verified by our team and indeed this is a bug in the SQL scrip generation. This bug is already being fixed so you will not have this problem after we release the next internal build on our web site. This should happen in the following two-three weeks. 

We have made several improvements in the area of creating associations between two entities for the latest internal build that we have released on our website. You should not have any problems dragging an association between two entities if you install that version of the product.

In oracle you are able to use Sequential Identity fields with OpenAccess. You should create and configure your sequence in your oracle server and then in the OpenAccess designer you should select the desired entity and for the property Identity Mechanism you should select the "Backend Calculated" value. That means that OpenAccess will not calculate that field but it will leave the backend database server to calculate it for us - the same setting applies for SQL server AUTOINC members.

I hope my answer sheds some light on your issues with Telerik OpenAccess ORM - if you have any further questions/suggestion please do not hesitate to contact us back. We are looking forward into improving our product so that it satisfies all of the expectations of our clients and the Oracle clients are definitely a big and very important part of our client base.

Best wishes,
Zoran
the Telerik team