Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for EF's Migrations [DNET506] #490

Closed
firebird-automations opened this issue May 31, 2013 · 10 comments
Closed

Support for EF's Migrations [DNET506] #490

firebird-automations opened this issue May 31, 2013 · 10 comments

Comments

@firebird-automations
Copy link

Submitted by: @cincuranet

Is related to DNET503

Votes: 2

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue is related to DNET503 [ DNET503 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue relate to DNET503 [ DNET503 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue relate to DNET503 [ DNET503 ] =>

@firebird-automations
Copy link
Author

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.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Author

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.

@firebird-automations
Copy link
Author

Commented by: @cincuranet

It's not yet implemented (that's why the ticket is still open), so it's expected.

@firebird-automations
Copy link
Author

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).

@firebird-automations
Copy link
Author

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.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: In Progress [ 3 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: vNext [ 10722 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants