Hello,

I'm currently facing a problem. I've just modified my database and replaced most identity pk's with UNIQUE IDENTIFIERS (guid), The default column value is NewID(). I did this in order to make my DB more replication and synchronization friendly(New requirement). So now I have to massively update my source code. But I get a lot of unexpected behavior because my entities don't retrieve the NewID after being saved. I searched the forum and saw that some folks had reported this in april 2008 (about SQL SERVER CE i think).  For your information, I  generated my "generated" classes after having modified  the database and I am not using SP.

Would it be possible fix this in the next maintenance release? I know it's due sometime early next week, but it'd be life saving. The work around would be to generate the guid myself but this would the last option.

In case your tests don't show anything weird, could I have some advice on how to fix this?  I mean a fix, not a work around that'll take an enormous amount of time to implement (no offense).

--------------------------------------------------------------------
Quick edit:  EntitySpaces 0623  VistaDB build 57
--------------------------------------------------------------------
 

Thank you for your time. Unfortunately setting the default value to GUID() instead of NewID() didn't help (I regenerated the classes after applying the new default value). However inheriting from a custom base class in which the Save() method is overridden seems to do the trick just fine and didn't take much time to implement as you can see  :

In fact, I overloaded the entity.addnew() method.

    Public Overrides Sub AddNew()
        MyBase.AddNew()
        'I am not looking for composite keys
        If Me.Meta.Columns.PrimaryKeys.Count = 1 Then
            'Only if the PK has a datatype of Guid
            If Me.Meta.Columns.PrimaryKeys.Item(0).Type Is GetType(Guid) Then
                Me.SetColumn(Me.Meta.Columns.PrimaryKeys.Item(0).Name, Guid.NewGuid)
            End If
        End If

    End Sub

But since that, I've been having some weird behavior, like inserts that work well but update that don't commit ( exceptions saying that 0 rows were affected instead of 1) or that throw concurrency errors, especially when wrapped in a "using scope as new esTransactionScope" clause and on collection.save(). When replace my saves by sql update queries, everything is runs just fine.

Do you think the overloaded AddNew() method could be the cause of all this? As I said in a previous post, everything was running fine before I changed my identity PK's to UniqueIdentifier's.

It's a bit hard to provide a sample project that reproduces these errors... would it be possible to have entityspaces retrieve the new guid primary key on inserts on the next maintenance release ?
 

The one thing about calling SetColumn() is that it doesn't mark the column as dirty.

Try adding this to your code after you call Me.SetColumn()

Me.MarkFieldAsModified(Me.Meta.Columns.PrimaryKeys.Item(0).Name))

Thanks, I've added this line of code but it doesn't seem to change much.

I think the best solution would be not to overload AddNew() (therefore not interfering with RowState and stuff) ... but that is only possible if EntitySpaces retrieves the NewID() for me