Recommended WCF RIA Implementation/Table Structure?

4 posts, 0 answers
  1. Scott
    Scott avatar
    42 posts
    Member since:
    Feb 2009

    Posted 11 Apr 2011 Link to this post


    This thread is related to another thread titled, "database table structure." Sorry for the overlap, but we're struggling to understand the recommended approach for persisting RadScheduleView Appointments to the database via WCF RIA Services. Questions:

    1. Do you have a more refined reference implementation solution similar to
    2. What is the proper structure for persisting Appointment recurrences and recurrence exceptions?
    3. Are you sticking with a virtually duplicated SqlAppointment entity (SqlExceptionAppointment) as the means to store recurrence exceptions?

    The MVVM-related improvements to the RadScheduleView relative to the RadScheduler are excellent--thank you. However the ScheduleView_EF_SL sample is a bit confusing because of the switch away from implementing exceptions storage as self-referencing SqlAppointments. In addition, there appear to be columns left over from the self-referencing example (SqlAppointments.ParentId for example) that do not appear to be used in the sample.

    Because we have a large solution, changing our database schema, Entity Framework data model, WCF RIA Service meta-data classes, and RIA [query], [update], etc., classes is a time-consuming operation. I want to be sure I head down the recommended path sooner rather than later.

  2. George
    George avatar
    1332 posts

    Posted 15 Apr 2011 Link to this post

    Hi Scott,

    Thank you for contacting us again.

    I answered to some of your questions in the other thread. Our goal is to make as much as possible the RadScheduleView data binding MVVM friendly.

    The project is just an example how to achieve the scenario. Anyway, we left some of the properties blank because they require custom logic. 

    Please do not hesitate to contact us if you require any further information.

    Best wishes,
    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. Scott
    Scott avatar
    42 posts
    Member since:
    Feb 2009

    Posted 15 Apr 2011 Link to this post

    Hi George,

    Thanks for the info. Our biggest dilemma was how to implement the persistence of recurrence-related objects. Your description of them as distinct entities makes sense so we will add SqlException* tables/entities in addition to SqlAppointment table, and we'll remove the self-referencing bits.

  4. schneeflocke
    schneeflocke avatar
    31 posts
    Member since:
    Jan 2010

    Posted 10 Jan 2012 Link to this post

    Hi Scott,

    in your solution, have you used the M2M4Ria Logic as provided in the Telerik sample or was it not necessary to be used in your solution?


Back to Top