This question is locked. New answers and comments are not allowed.
Hi,
When you change Identitiy Mechanism for Guid column to DatabaseServerCalculated, the "Update Database From Model" wizard generates below script
ALTER TABLE [documents] ADD CONSTRAINT DF_Documents__document_id DEFAULT (newsequentialid()) FOR [_document_id]
However, newsequentialid() is not supported by SQL Azure (at least not yet).
(In model settings backend is set to Microsoft SQL Azure, OA v2012.1.329)
Not a big deal, but it made me think: what impact does this setting of the type of backend have on overall interface?
Jacek
When you change Identitiy Mechanism for Guid column to DatabaseServerCalculated, the "Update Database From Model" wizard generates below script
ALTER TABLE [documents] ADD CONSTRAINT DF_Documents__document_id DEFAULT (newsequentialid()) FOR [_document_id]
However, newsequentialid() is not supported by SQL Azure (at least not yet).
(In model settings backend is set to Microsoft SQL Azure, OA v2012.1.329)
Not a big deal, but it made me think: what impact does this setting of the type of backend have on overall interface?
Jacek
1 Answer, 1 is accepted
0
Accepted
Hello Jacek,
Petar
the Telerik team
You are correct and this is indeed a bug on our side that we have fixed now. The fix for this will be available with our next internal build/service pack. From now on we will be using newid() instead of newsequentialid().
This should not have any impact on your application as currently ddl script is created only for identities of type integer and guid. What this setting does is simply notifies our runtime that this ID will be generated by the database so that it is omitted in the sql statement we generated during inserts.
Please find your Telerik points updated for sharing this bug with us.
Petar
the Telerik team
Telerik OpenAccess ORM Q1 2012 release is here! Check out what's new or download a free trial >>