2. According to this: https://msdn.microsoft.com/en-us/data/dn456841.aspx there might be problem with ContextKey field because it is PK. But there is a workaround that allows to decrease size of the field. Don't know why this field need to be so long.
Do I need to fill tracker issues for described problems to track progress? -----Original Message----- From: "Jiří Činčura" <j...@cincura.net> Sent: 8/30/2015 9:08 AM To: "For users and developers of the Firebird .NET providers" <firebird-net-provider@lists.sourceforge.net> Subject: Re: [Firebird-net-provider] Migrations 1. I think table names need to be preserved. Developer is reponsible for checking for that constraint. The name is defined. But I meant generated names, like PK name (if not specified). It's same for column names etc. It would be pretty confusing to later open that database and see just weird characters. 2. AFAIK you still need 16k database to be able to make PK (or maybe just 8k is enough, not 4k for sure). 4. OK, that might be bug. -- Mgr. Jiří Činčura Independent IT Specialist ------------------------------------------------------------------------------ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
------------------------------------------------------------------------------
_______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
