Jonathan Pryor precisò: > Specifically, the specialized database generation logic should also use > the EntityInterfaces type (which should likely be simplified to -type or > something). That way a single option controls what types are generated, > and by implication will control whether the specialized DataContext is > generated (or not, again, based on the type's name). > > This would be straightforward and easily documentable (I hope).
I'll rework my patches such that instead of separated --generate-datacontext and --entity options a single --type option will do, but it's not clear to me how it should also replace --entityInterfaces. Also, we'd like that --type does not prevent references from being generated, such that (for example) if Order refers to the Customer table (which is not being generated in the current run) the reference Order.Customer will be available nonetheless. Otherwise we can investigate a more explicit approach with a --separate-files (or whatever you prefer) option. -- Emanuele Aina Studio Associato Di Nunzio e Di Gregorio http://dndg.it/ Via Maria Vittoria, 2 10123 Torino - Italy -- You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/dblinq?hl=.
