On Sat, 2009-11-14 at 19:47 +0100, Emanuele Aina wrote: > 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.
Evidently I wasn't thinking properly, as obviously those refer to two distinct concepts and thus should be separate options. That said, --type isn't very clear; perhaps --output-type or --generate-type would be better? I do wonder why we have/need --entityInterfaces, though -- what's the use case for wanting e.g. INotifyPropertyChanged but not INotifyPropertyChanging? Or is it to prevent generating the IModified interface? (By the way, I see an IModifiedImplementation type in DbMetal, but not an IModified interface. I also don't see an IModified interface in Mono, so I'm not even sure what this looks like...) So to a certain extent, I'm inclined to just remove --entityInterfaces and just always generate the appropriate interfaces (both INotifyPropertyChanged and INotifyPropertyChanging, as L2SQL does). > 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. This makes perfect sense, and I'm not sure any other way would make sense. Thanks, - Jon -- 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=.
