Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > LLBLGen Pro Runtime Framework> Can I avoid having ORMConcurrencyException thrown when entities don't exist?
 

Pages: 1
LLBLGen Pro Runtime Framework
Can I avoid having ORMConcurrencyException thrown when entities don't exist?
Page:1/1 

  Print all messages in this thread  
Poster Message
JimFoye
User



Location:
Austin, TX
Joined on:
22-Jun-2004 04:03:11
Posted:
656 posts
# Posted on: 07-May-2008 02:39:47.  
I have a situation where I really would like to avoid having ORMConcurrencyException thrown during an update if the entities don't exist anymore. (I know someone will ask why, but just take my word for it).

I know I can loop through all the entities and manually check each one to see if it still exists before updating, but it'd be a lot simpler if I could just let the updates silently fail if they don't exist anymore. Is that possible?
  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14626 posts
# Posted on: 07-May-2008 10:25:18.  
I can see no other way to do it except building your own version of the ORMSupportClasses...dll

  Top
JimFoye
User



Location:
Austin, TX
Joined on:
22-Jun-2004 04:03:11
Posted:
656 posts
# Posted on: 07-May-2008 19:24:35.  
Ok, I understand the reasoning for it, but in my case I am saving off some data, then deleting and repopulating those tables, then saving back the data - but some of those records may no longer exist, in which case I don't care.

No problem, I'll just have to manually verify which records still exist before doing the update.

Thanks.
  Top
Pages: 1  


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

Version: 2.1.12172008 Final.