Initial Issues

4 posts, 0 answers
  1. Ron Buchanan
    Ron Buchanan avatar
    6 posts
    Member since:
    Dec 2009

    Posted 29 Apr 2010 Link to this post

    I have been using various ORMs for several years, currently using NetTiers. We are also considering DataObjects.NET but do not like the idea of it changing the database schema. We deal with a lot of data and so our database structures are decided with a purpose, and so anything that wants to change that, I have a problem with.

    Since we are a customer of Telerik for the ASP.NET RadControls, I have started experimenting with the latest version of OpenAccess v10.x. Here are some initial things that I have noticed out of the box:

    Environment:

    SQL Server 2008
    Visual Studio 2008

    1. We use schemas beyond the default 'dbo' in SQL Server. Typically, when creating a new ORM layer, we do an ORM library at the schema level, not DB level. So, when going through the OpenAccess wizard, I selected Prefix with SchemaName. I also like my entities to be suffixed with the word Entity and prefer attributes over XML. The end result had 2 major problems that I saw:
         a. The entities were not prefixed with the schema name.
         b. The attribute had a syntax error on each entity. OpenAccess generated this
               [Table("MyTableName"SchemaName = "schema", )]
             rather than this
               [Table("MyTableName", SchemaName = "schema" )].

    2. I left all settings for capitalization to remain unchanged. I have found that if the capitalization is done correctly in the DB, then ORMs typically do what you want. I also selected for the collections to be pluralized rather than singular. The problem that I am noticing is this in the capitalization of the collections:

         Table Name = OrderDetail   ---> correct
         Entity = OrderDetailEntity   ---> correct
         Collection = Orderdetailentities  ---> incorrect, why not OrderDetailEntities?

    3. I have not quite figured out what will be called what when it comes to the wizard and what the file will be called vs. what I have to use in the code for the context. Everything wants to default to the same. I would like to have the following like so (any help would be good):

         Database Name = Accounting
         Connection = AccountingConnection
         Model = AccountingModel
         Context = AccountingModelContext

    This is what I have noticed so far. Any help would be appreciated.
  2. Zoran
    Admin
    Zoran avatar
    534 posts

    Posted 03 May 2010 Link to this post

    Hello Ron Buchanan,

     Thanks for the feedback. These are actually all known issues and they were fixed for the latest internal build that we published on our web site the previous month. You can download it from there and try it out. These issues should no longer be part of the user experience.

    Kind regards,
    Zoran
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
  3. DevCraft banner
  4. Ron Buchanan
    Ron Buchanan avatar
    1 posts
    Member since:
    Sep 2009

    Posted 03 May 2010 Link to this post

    I am using version 2010.1.312.2 which I downloaded and installed just last week. I had the previous version and made sure I uninstalled before installing the new version. Is this the correct version?
  5. Zoran
    Admin
    Zoran avatar
    534 posts

    Posted 03 May 2010 Link to this post

    Hi Michael Sostarich,

     Actually it seems that there is some misunderstanding as Telerik OpenAccess ORM never released such version. The latest version of our product is 2010.1.414.3, it is an internal build and the official release is 2010.1.312.2.

    You can check the installed version in visual studio from the Telerik menu: Telerik -> OpenAccess -> Help -> Product Info.

    Sincerely yours,
    Zoran
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Back to Top