Timestamp column incorrectly mapped

2 posts, 0 answers
  1. Jonathan Simmons
    Jonathan Simmons avatar
    108 posts
    Member since:
    Jun 2005

    Posted 20 Jul 2010 Link to this post

    Upgraded to 2010 Q2 and using VS2010.

    Just reverse-mapped a database where a number of tables have a timestamp column. The domain modeler seems to think that this is an autoincrement field for some reason as I now get the error:

    Error 6 The column AuditTimestamp is specified as an autoincrement but it is not a primary key column
     
    The column definitely is NOT marked as an autoincrement field as it is a timestamp and therefore could never be an autoincrement field!!! And certainly I would never set a timestamp as a primary key!

    Where has this new error come from?

    Regards,
    Jonathan
  2. Serge
    Admin
    Serge avatar
    375 posts

    Posted 20 Jul 2010 Link to this post

    Hi Jonathan Simmons,

     First sorry for any inconvenience caused. This is in fact a bug on our side. It is an error in our validation system which is already fixed and it will be available in the next release. As this is not preventing compilation nor is it in any way interfering with the runtime please bear with this until the first release.

    When you upgrade to the new version it will not be shown any more. I will notify you in this thread once we have published a new release. Please find your Telerik point updated for bringing this problem to us.

    Greetings,
    Serge
    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
Back to Top