Unfortunately this is part of a much larger project. Forgive me if this shouldn't be logged here or I have done something stupid, publishing migrations doesn't seem to apply the Identity flag to a column but only on Sql Server. Migrations are currently only generated based on the active provider (SQLite).I'm using Open Iddict with Identity to generate the base schema for the database. You'll need to compensate for any additional providers you intend to run the migrations on.In the first section the table is created with a "Generated Always Identity" column.

updating an identity column-39

Consider a table that looks like this: Columns with the identity property-or, as they are more familiarly known, identity columns-are most frequently used to ensure uniqueness, generally as a primary key.

While GUIDs, also know as unique identifiers, can also be used to ensure uniqueness, they have their own set of problems.

You will need to alter the table and drop identity, then perform your update; restore Identity (another Alter statement) and reset Identity value (if needed, because of your updates).

This can only be done without potential loss of data integrity, if you temporarily block access to this table, e.g. If you are talking about a brand new column, a better approach will be to add this column as a regular column, update it by using, say, recursive SQL, then ALTER the table, make it identity and RESTART the value.

One final remark: an identity column is not the same as a primary key.

If you want to use a "Generated Always Identity" column as your primary key, then you will have to specify that explicitly.

(For more information on using GUIDs as PKs, please refer to

id=2504.) When you create an identity column, you can specify a start value called a seed and an increment value called an increment. There are three caveats associated with identity columns: You can use any real number as a seed or increment; positive and negative numbers are valid, but fractional, decimal or imaginary numbers are not.

--- /sites/all/modules/eck/eck.classes - Mon Sep 16 2013 sites/all/modules/eck/eck.Mon Sep 16 2013 @@ -84,14 84,15 @@ [email protected] If you are using SQL Server, the Drupal 8 driver (8.x-2.x) has been expanded to deal with such situations in order to provide better compatibility with the default My SQL behaviour. If you are using SQL Server on Drupal 8 and experiencing this issue with the 8.x-2.x please provide steps to reproduce and will take a look at it. Hi David, I see you are the brain behind Drupal support for Windows. Would be nice if 8.x-1.x branch would at least be in a state of *working* without bells and whistles...