design issues on 3 tier architecture

Last post 08-02-2007, 10:28 AM by Eric Russell. 1 replies.
Sort Posts: Previous Next
  •  03-21-2007, 12:17 PM Post number 21112

    • TaLz is not online. Last active: 03-21-2007, 2:09 PM TaLz
    • Not Ranked
    • Joined on 03-22-2007
    • Level 1: Deep thought

    design issues on 3 tier architecture

    hello,

    i'm trying to design a 3 tier architecture but have come on a few problems.

    i want the DAL layer and the BO layer to communicate via objects.

    every object has a unique id.

    for example an object task has an id that is generated by the database.

    i want the DAL layer to set the id of this field when performing save for the first time.

    i don't want the BO layer to be able to set this field.

    how can this be done?

    thanks,

    TaLz

     

  •  08-02-2007, 10:28 AM Post number 34330 in reply to post number 21112

    Re: design issues on 3 tier architecture

    In SQL Server Books Online, read into the use of the IDENTITY option on columns. When a row is inserted, the value of the identity column will assigned an incremented integer value.

     

View as RSS news feed in XML