Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > LLBLGen Pro Runtime Framework> Identity Keys - Making my own
 

Pages: 1
LLBLGen Pro Runtime Framework
Identity Keys - Making my own
Page:1/1 

  Print all messages in this thread  
Poster Message
ianvink
User



Location:

Joined on:
15-Dec-2006 02:36:45
Posted:
358 posts
# Posted on: 21-Sep-2007 21:07:24.  
Our system runs on multiple data centers in different countries. We need to roll up values from tables into a warehouse. So we need a unique key for each record, ints of course not being an option.

Guids are too slow. (see: http://www.informit.com/articles/article.aspx?p=25862&rl=1 )

So we have a function that will return a unique key that doesn't have the same performace penalty (see same article for the generator).

Is there a way with version 2.5, SelfServicing, to tell the system to use this function as it's unique key generator instead of relying on @@Identy etc?

I can override every entity collections' EntityAdding function, but would rather have a way to specify it, perhaps with Dependency injection?

Thanks,
Ian
  Top
JimHugh
User



Location:
Davis, CA
Joined on:
16-Nov-2005 14:32:25
Posted:
191 posts
# Posted on: 21-Sep-2007 21:32:32.  
If there is any chance you can use SQL 2005 instead of 2000, you may want to look at NEWSEQUENTIALID(). Still a GUID, but eliminates some of the concerns in the referenced article.

Do a Google search to see some of the pros and cons.


Jim Hughes  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14626 posts
# Posted on: 24-Sep-2007 10:39:05.  
Maybe you just need to use a common base Validator to validate the entity before save, to call your method and set the Unique field.
  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.