database - Linq to Sql Data class in dbml -
I'm curious about DBML ... should I make a DBML file for a database or a sad user dbml ( Only related to table users) etc.? When I do this, I will have to face problems, assuming that the user has a user table in DBML and if the order is also a user table in the DBML, this permission will not be allowed if the entity name space is the same. If I have set a separate entity namespace for each DBML, then it works but it will give me a separate unit of user table. When any data returns to business logic layer, it is difficult to know which unit's namespace is used to use the user table.
If I had created a DBML file instead of separate DBML, then the single DBML will appear when getting data from the database slow while compared to the different dbml version.
From Linux, the SQL is designed to operate with a single data reference object.
Lifetime of SQL datacontent with a LINQ
Using a repository pattern, the Nerd Dinner Tutorial is a very good example of SQL usage from specific Linux. In all cases, repository objects use a data context object to work:
What are you trying to do, as it may be more appropriate. However, advise that there are some problems with the current release of the unit framework, especially regarding lazy loading.
Comments
Post a Comment