You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There does not currently (in v1.0 RTM) seem to be a way to choose which field can have a clustered index created.
I believe that previously, before the rewrite, it was possible to set this. Now the clustered index always appears to be set on the first column of the primary key.
I suggest modifying either IClassInstance or IPropertyInstance to support this functionality.
Especially when using Guids for primary keys, it useful to cluster on something other than that key.
The text was updated successfully, but these errors were encountered:
There does not currently (in v1.0 RTM) seem to be a way to choose which field can have a clustered index created.
I believe that previously, before the rewrite, it was possible to set this. Now the clustered index always appears to be set on the first column of the primary key.
I suggest modifying either IClassInstance or IPropertyInstance to support this functionality.
Especially when using Guids for primary keys, it useful to cluster on something other than that key.
The text was updated successfully, but these errors were encountered: