Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-30 Thread Sibylle Koczian
Am 28.09.2012 15:01, schrieb Jiri Cincura: > Use null as initializer. > Thank you, that works. But it means that I can neither create nor change my database schema from the application. Only "code first with an existing database" is possible, right? Not really a problem, but I'd like to know for

Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-28 Thread Jiri Cincura
Use null as initializer. -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast

Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-28 Thread Sibylle Koczian
You have Migrations turned on, but Migrations are/is not supported (currently).How can I turn off Migrations? I don't want them for the moment. I would have thought using a Database Initializer derived from DropCreateDatabaseIfModelChanges<> would turn them off, because that seems incompatible with

Re: [Firebird-net-provider] Entity Framework 5, code first: database created, then crash

2012-09-27 Thread Jiri Cincura
You have Migrations turned on, but Migrations are/is not supported (currently). -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com -- Everyone hates slow websites. So do we.