TableOptions.IdentityColumnSize By default is set to int32 instead of int 64

[giannik]

In latest version when I create a custom table index im getting an exception :

Microsoft.Data.SqlClient.SqlException (0x80131904): Column 'Document.Id' is not the same data type as referencing column 'PhoneNumberAssetContentItemIndex.DocumentId' in foreign key 'FK_PhoneNumberAssetContentItemIndex'

because the DefaultIdentityColumnSize is int32 instead of int64.
Has something changed from yessql That makes int32 the default?
If I set the DefaultIdentityColumnSize =int64 from appsettings then it works .
@MikeAlhayek @sebastienros

[MikeAlhayek]

Tenants that were created in older version of OC "I don't recall exactly but I think 1.7" will have int32 size. New tenants will have a default of int64

[giannik]

Is that a setting we could change for old tenants manually , to avoid having to change the global settings in appsettings.json ?

[MikeAlhayek]

It's not configurable. It's a behavior that is built in the system depending on when the tenant was created. You should not have to make any change from your end and it should work.

Here is where it's documented

https://docs.orchardcore.net/en/latest/releases/1.7.0/

If a tenant was created < 1.7, the default is int. Any site was created in version 1.7+, will default to long. For new tenants we add settings in the tenant setting indicating that this tenant uses long.

So you can't manually update the appsettings for that tenant because it all depends on when the tables were created and we maintain the same is types.

If you manually updated the appsettings, then you have to modify every table manually to long. Every identity column and DocumentId column

[giannik]

Got it. So basically just go to the old tenant appsettings and add the same settings there. Thanks

…

On Wed, Jan 29, 2025 at 7:56 AM Mike Alhayek ***@***.***> wrote: It's not configurable. It's a behavior that is built in the system depending on when the tenant was created. You should not have to make any change from your end and it should work. Here is where it's documented https://docs.orchardcore.net/en/latest/releases/1.7.0/ If a tenant was created < 1.7, the default is int. Any site was created in version 1.7+, will default to long. For new tenants we add settings in the tenant setting indicating that this tenant uses long. So you can't manually update the appsettings for that tenant because it all depends on when the tables were created and we maintain the same is types. If you manually updated the appsettings, then you have to modify every table manually to long. Every identity column and DocumentId column — Reply to this email directly, view it on GitHub <#17417 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALSLNJM6DZRX6GAHVQ3FH32NBUP5AVCNFSM6AAAAABWBPTSXSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJZGE3TOMA> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[MikeAlhayek]

You should not need to make any change for it to work. Did you by mistake try to force old tenants to using int64?