Geek Answers Handbook

Which template most closely matches the scenario, and is this good practice?

Over the past few years, I have seen a specific sample several times. Please let me describe this.

In the user interface, each new record (for example, new customer data) is saved in the form without being saved in the database. This is clearly done so as not to clutter up the database or create unnecessary database hits.

In the user interface state, these objects are identified using Guid. When they are saved in the database, the associated Guides are not saved. Instead, they are assigned the Int database as the primary key.

A form can handle mixing up the extracted elements from the database (using Int), as well as those that have not yet been completed (using Guid).

When checking the form (using Firebug) to find out which key was used, we found that a combined key with two-part separators was used. The first part is guid (an empty manual if it is removed from the database), and the second part is an integer (zero is preserved if it is not extracted from the database). Since one part of the combined key will always uniquely identify the record, it works pretty well.

Is this a good practice or not? Can someone tell me the name of the template or suggest it if it is not already named?

+5
source share
3 answers

There are a couple of patterns here.

ID field pattern

P EAA " , in-memory ". .

Script

, ASP.NET DataBound - Transaction Script > . Fowler " - ". - , .

Transaction Script - , . " , , , :

  • , .
  • , , - .

Guid integer , . (, , UI), , , .

?

. ASP.NET - , , , . - ASP.NET - . , . , Row Data Gateway. - , . Active Record, Domain Model Repository .

, . , , . , , , , .

+4

, .

? . -, -. :

interface ICommittable
{
    /// <summary>
    /// Gets or sets a value indicating whether the entity was already committed to the database.
    /// </summary>
    bool IsCommitted;

    /// <summary>
    /// Gets or sets the ID of the entity, used either in database or generated by UI or an underlying BL.
    /// </summary>
    Guid Id;
}

:

  • (?)
  • , .

, , , , .

, GUID : , Guid.CreateNew , , , , GUID ( , GUID , ).

, ?

. , ? , :

  • , GUID, ,
  • , , ,
  • , GUID .

, . , , id (int) , GUID, :

  • ,
  • .
0

If I'm not mistaken, this is the repository template: http://martinfowler.com/eaaCatalog/repository.html

This is well described in the Evans Domain Driven Design book of design and has proven effective in certain circumstances.

-2
source

More articles:


All Articles