> But then we're back where we started. Question is whether the global > definition for whole migration generator or per column is more > understandable and discoverable for developers. If question only about this, then my opinion that it must be fine-grained at a column level. But there should be a possibility to set an implementation for context wide. It will cover the case where you use mixed scheme: all tables have one generator, except several that have per table generators. You specify context-wide implementation per database generator, and in ModelBuilder you specify generators for these exceptional tables.
On 1 October 2015 at 22:26, Daniel Rail <dan...@accra.ca> wrote: > Hi, > > At October 1, 2015, 2:21 PM, Jiří Činčura wrote: > >> On Thu, Oct 1, 2015, at 19:00, Геннадий Забула wrote: >>> In ModelBuilder you can specify any object as data annotation. In this >>> case user can provide implementation of the interface. > >> But then we're back where we started. Question is whether the global >> definition for whole migration generator or per column is more >> understandable and discoverable for developers. > > My preference would be at the column level. Since that would be more > discoverable for me, because it is close to where it is used. > > -- > Best regards, > Daniel Rail > Senior Software Developer > ACCRA Solutions Inc. (www.accra.ca) > ACCRA Med Software Inc. (www.filopto.com) > > > ------------------------------------------------------------------------------ > _______________________________________________ > 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
