can1 wrote:
There is no AdapterGenericNamespaceSuffix, only an AdapterDbSpecficiNamespaceSuffix.
So, all db specific namespaces, must always be a sub namespace of of the generic namespace?
Can1
That's indeed an oversight in the current codebase and my mistake in suggesting that this option is available.
This doesn't have to be that bad. The idea is that code is generated for the generic project once, and then code is generated for the db specific side, and if you support more than one database type, the db generic project for other databases is not used anyway.