![]() ![]() ![]() Yes, hm, I read the thorough analysis in craftycodeblog, but wouldn't it be nice if you could get all the benefits from both sides? Note that the converse is not a problem, i.e., one can have a single DBML file containing multiple groups of entities that are not related to each other by any associations. Generically speaking, one can have multiple DBML files if each DBML file contains all entities and relationships that are connected. Going back to our example, if there was no relationship between tables A and X in database D, then one would be able to create 2 DBML files. If some tables or constraints are missing from a set of DBML files, then the set of DBML files do not accurately reflect the underlying database. To my mind, a DBML file reflects the data-model represented by the tables and constraints on those tables in a database. This is the single biggest problem with having multiple DBML files. Say you have 2 DBML files P and Q based on database DĪFAIK, there is no way for DBML files P and Q to contain an association between entities A' and X'. ![]() Table X also has a foreign key relationship with table A.Database D contains tables A, B, C, X, Y, Z where ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |