When i save new entity using adapter, i don't see my PK. PK GUID is created in SQL.

// --------------- BookEntity newBook =new BookEntity ()

newbook.Name= "Some Book"; newBook.AuthorId=4;

ataAccessAdapter adapter = new DataAccessAdapter(); adapter.SaveEntity(newBook,true); MessageBox.Show(newBook.BookGUID.ToString());

//----------------

shows "0000-00-000...."

it did save the book,but why dit don't i see the BookGUID when i have refetchAfterSave=true?

A guid cannot be retrieved from the DB like an identity column can be. For this type of scenario you need to set the Guid before you execute your save.

// ---------------
BookEntity newBook =new BookEntity ()

newbook.Name= "Some Book";
newBook.AuthorId=4;
newBook.BookGUID = Guid.NewGuid();

ataAccessAdapter adapter = new DataAccessAdapter();
adapter.SaveEntity(newBook,true); 

Thanks for your response.

This is my first real disappointment with LLBLGen. We use Guids exclusively for entity PKs (excluding some system tables that need to have corresponding enums). I hit this problem today and found this post, as well as another.

So, now I need to use Guid.NewGuid when saving an entity that is new... not that big of a deal I suppose, except that with SQL 2005, we have sequential guids available, which provide better indexing. So with LLBLGen, we can't take advantage of this feature.

Oh well. Still lovin' my first LLBLGen project :-)

Of course you can take advantage of that feature, in LLBLGen Pro v2.0 support for NEWSEQUENTIALID() is build in. Simply define the default as NEWSEQUENTIALID() and you're good to go. Only works for PK's. Don't set the PK to a value.

Wow, I'm an ass. A search for NEWSEQUENTIALID() in the documentation clearly describes how to take advantage.

Well, alrighty then. Back to zero disappointments with LLBLGen

Thanks Frans!

Pfew