OpenAccess inserts 0 for PK field in Oracle

Thread is closed for posting
3 posts, 0 answers
  1. DMC Helpdesk
    DMC Helpdesk avatar
    52 posts
    Member since:
    Nov 2007

    Posted 21 Jun 2010 Link to this post


    I am  using the visual designer to model my entities and one my entities is using oracle sequence and trigger to insert the PK field value.I used OpenAccess Data source to bind the FormView control to my entity.When the formview inserts the record, everything is fine except that the primary key value is inserted as 0 .The OA should actually pass null value, so that my trigger can do the sequence insert.

    begin     if inserting then       if :NEW."ID" is null then          select SEQ_INVENTORY_MOVEMENTS_ID.nextval into :NEW."ID" from dual;       end if;    end if; end; 

    Your help is much appreciated.


  2. DMC Helpdesk
    DMC Helpdesk avatar
    52 posts
    Member since:
    Nov 2007

    Posted 22 Jun 2010 Link to this post

    After 3 weeks of struggling with OpenAccess, we decided to drop the use of OpenAccess from our solution.We think the product is still not mature yet especially when used with oracle backend.There is no clear indication of when to use reverse-mapping and when to use the visual designer modeling.Most of the examples and courseware are based on the reverse-mapping and ignores the visual designer modeling approach.The documentation also mix these 2 approaches and jump from 1 approach to another.I also feel the forum support is taking longer to respond, and for every issue i face, i need to wait 2 days for a response.


  3. Zoran
    Zoran avatar
    534 posts

    Posted 24 Jun 2010 Link to this post

    Hello DMC Helpdesk,

     First let me apologize for the inconvenience our tool has caused you. It is indeed in the stage of re-design and major development effort is being put into it for the last few months. That can really cause confusion for some of the customers and we are really sorry for this. The visual designer does not yet have all of the features required for the complete story which was available with the old wizards but that is something we will release in the Q2 release - a feature complete visual designer, able to provide forward and reverse mapping capabilities. The documentation is also in a major re-design stage and it will cover all of the development stories with the use of the Visual Designer.

    As for this particular issue, the sequential identity handling, is implemented in the product, however this is just a UI setting that the first version of the visual designer is missing and it will definitely be part of it in Q2 (three weeks from now). 
    Our team would like to thank you for using our product and we really hope to have again as our customer in the future when OpenAccess ORM indeed gets the required maturity for some more complex scenarios that you are handling in your application.

    Regarding the response time for your issues, the answer time for a forum post is 72 hours as defined in our company support policies. As a customer, you could send us support threads instead of forum ones which increase the priority of the issue to 24 hours. This applies for any of the product from our company so please have that in mind in case you have more urgent problems that need to be handled by our teams.

    Kind regards,
    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