Re: [Firebird-net-provider] Migrations

[Jiří Č. <ji...@ci...>]

> 1. Long names of tables causes foreign key script creation fail with error "Name exceeded implementation limitation". This caused by 31 characters limitation to almost anything not only FK. We crutched this with hashing names   with base64 convert. Ugly but works.

Maybe we can, in case it's longer than 31 characters, simply use GUID. Not nice either, though.

> 2. Second it is drop from support databases with pages less than 16384 because of another impl. limitation for max string field length. This breaks creating MigrationHistory table. We didn't fixed this, because started using separate database. But in near future our previous database would also need to have migrations. I think this can be crutched to use blob field only for Model field of this table.

You mean the PK on MigrationHistory? We can specify 16k page size as a requirement. There's not much to invent on the PK.

> 3. Issue with sequence generators. Maybe you remember discussion about this on github. Looks like I've found good place to configurate particular field. It is in OnModelCreating Properties().Configure(x=>x.AddAnotation()) for property. There user can specify what sequence behavior does he need or provide custom.

True. And with custom convention it's not even needed to specify it explicitly for every column.

> Today I tried to add tests for all this to repo but found out that we need to add separate test infrastructure for EF tests.

There's few tests I wrote. Using CF as that's easy to set up. But maybe the migrations would need deeper setup.

-- 
Mgr. Jiří Činčura
Independent IT Specialist