Closed firebird-automations closed 8 years ago
Commented by: Mark Junker (fubar-coder)
Is this even possible? I tried this but this is the error I get:
SetUp : FirebirdSql.Data.FirebirdClient.FbException : unsuccessful metadata update key size exceeds implementation restriction for index "PK___MigrationHistory" ----> FirebirdSql.Data.Common.IscException : unsuccessful metadata update key size exceeds implementation restriction for index "PK___MigrationHistory"
I cannot see how this might be possible due to the servers key size restriction.
Commented by: Mercea Paul (paul.mercea)
With new project, after first run, db generated and tables created (including __MigrationHistory). Enabling migration generate an error: Checking if the context targets an existing database... No MigrationSqlGenerator found for provider 'FirebirdSql.Data.FirebirdClient'. Use the SetSqlGenerator method in the target migrations configuration class to register additional SQL generators.
Commented by: @cincuranet
It's not yet implemented (that's why the ticket is still open), so it's expected.
Commented by: @cincuranet
This ticket is blocked by bug in EF (http://entityframework.codeplex.com/workitem/2683). Implementation is done-ish (https://github.com/cincuranet/FirebirdSql.Data.FirebirdClient/tree/migrations).
Commented by: Zvjezdan Tomicevic (zeko)
I believe that this can be directly tied to issue DNET621, which is resolved for next version. If schema was created by default create database statement with page size of 4096, some indices (for example index on varchar(128) field) are not possible. You get key size exceeds implementation restriction for index error. If database is created with 16384 (which is firebird 3 default anyway), then there is no problem. So this might already be fixed.
Submitted by: @cincuranet
Is related to DNET503
Votes: 2