I'm just curious. Is it possible to have too large a mapping file?
My mapping file is coming up on 1500 lines.
It is becoming a nightmare to manage.
Is it possible to use multiple mapping files?
I was thinking along the lines of splitting into USERDATA and CONFIGURATION DATA, which are the 2 types of data it returns.
The USERDATA represents tables the user works with, etc... the CONFIGURATION data is program configuration settings, etc...
This would make it easier to work with, but I'm not sure of the implications in doing so.
Adam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not necessarily.
My application has a lot of it's configuration data stored in the database, as it makes it easy to replicate changes to the app throughout all clients.
Approximatley 20-30 tables.
Application data is actual customer records, etc...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Microsoft XML parser doesn't currently support the XInclude syntax. There is a parser called XInclude.NET that does (it's mentioned in MSDN) but I'd rather stick to "out-of-the-box" XML handling for the moment.
I'm just curious. Is it possible to have too large a mapping file?
My mapping file is coming up on 1500 lines.
It is becoming a nightmare to manage.
Is it possible to use multiple mapping files?
I was thinking along the lines of splitting into USERDATA and CONFIGURATION DATA, which are the 2 types of data it returns.
The USERDATA represents tables the user works with, etc... the CONFIGURATION data is program configuration settings, etc...
This would make it easier to work with, but I'm not sure of the implications in doing so.
Adam
Sorry for the delay in responding - it's been busy :-)
Sorry but currently there is no way to support multiple mapping files.
I assume that configuration data refers to the database connection information, and not application specific data?
- Richard.
Not necessarily.
My application has a lot of it's configuration data stored in the database, as it makes it easy to replicate changes to the app throughout all clients.
Approximatley 20-30 tables.
Application data is actual customer records, etc...
Ah, I see.
So you'd like to make a mapping file something like
<database ...>
<parameter ... />
</database>
<xi:include href="AppConfigMappings.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
<xi:include href="UserDataMapping.xml" xmlns:xi="http://www.w3.org/2003/XInclude"/>
The Microsoft XML parser doesn't currently support the XInclude syntax. There is a parser called XInclude.NET that does (it's mentioned in MSDN) but I'd rather stick to "out-of-the-box" XML handling for the moment.
For your reference - If you want to see more about XInclude have a look at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxmlnet/html/xinclude.asp
- Richard
That's exactly what I'm looking for.
It would allow furthur granular management of the mapping file(s).
I agree that it is best to stick to the MS xml parser. Hopefully they will add this feature.
If I get too bogged down, perhaps I'll try implementing XInclude.NET and share my findings here.
I'll probably hit a few thousand lines before my app is done.
It might be better if some more work gets put into the mapping utility.
That way, it wouldn't really matter how large the mapping file is, since it can be managed visually via the utility.
Have you looked at it yet?
- Richard