For the Mono testing effort, I would like to use Sqlite with Mono's
System.Data.Linq.dll, without using DbLinq*.dll (as the necessary
drivers will be built into Mono's System.Data.Linq.dll).
This sounds easy, but is unexpectedly non-trivial because the test code
uses the MONO_STRICT define to mean two unrelated things:
1. Use the System.Data.Linq namespace instead of the
DbLinq.Data.Linq namespace (what I want/need).
2. Use the MsNorthwind namespace and not the nwind namespace for
the generated Northwind database types (e.g. the Customer class,
etc.).
(2) causes things to fail badly when I try to make things Just Work
while using Sqlite.
Thus, a question: Why do we have this state of affairs, in which the
generated Northwind database types are in a different namespace for SQL
Server vs. everything else?
It would be far cleaner if all generated types were in the same
namespace, and would allow removal of MONO_STRICT from a number of test
files that just need the Northwind types but not the
System.Data.Linq/DbLinq.Data.Linq namespace distinction.
The fix is straightforward: Modify
examples/DbLinq.Mssql.Example/nwind/originalMSNorthwind.designer.cs and
place the types into the nwind namespace, and update all the test files
to no longer reference the MsNorthwind namespace.
Is there any reason to not do this?
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]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---
