> That's why the interface with some default implementation is so convenient. In ModelBuilder you can specify any object as data annotation. In this case user can provide implementation of the interface.
On 1 October 2015 at 19:01, Jiří Činčura <j...@cincura.net> wrote: > On Thu, Oct 1, 2015, at 13:38, Геннадий Забула wrote: >> I'm talking about "generator creation", it should be hidden in the >> provider. Though names yes, user should be allowed to pick a naming >> scheme he wants. >> In case "one generator for all tables" user specifies one generator >> name for all tables and provider should check if it exists - nothing >> to do, if not it creates new. After that it binds the generator name >> to before insert trigger. > > Well that's just part of story. You also need to name the trigger. You > need to have the body. Some people use like `Id is null` clauses. Some > also include 0 or -1 (for integers) etc. Not sure how to code this using > annotations (without implementing all possible combinations). That's why > the interface with some default implementation is so convenient. > >> > Well, the default initializers are using different path. >> Yep, I'm aware about this. First I've patched one code path. After >> merge the migration feature I needed to patch another code path, and >> resulting database had differences. > > I'd like to eventually re-use parts of migrations code to have (almost) > same result. > > -- > 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
