Although this is something common with plain SQL, ORMs work a bit differently. Tables in the database are mapped to classes and all database interaction (reading and writing) is mostly done via these set of classes.
Performing a LINQ query that joins several types ( each type in turn is mapped to a table) results in a type that has fields (i.e columns) from several types clubbed together in an anonymous type. The ORM knows only about the persistent types defined in the domain model and can manage changes to these types.
You can select the types in the LINQ query and then update properties of the individual types.
var u = (from user
db.AccountTypes on user.AccountTypeID equals acttype.AccountTypeID
db.Credentials on user.CredentialsID equals creds.CredentialsID
db.MobiCarriers on creds.MobiCarrierID equals mobicar.MobiCarrierID
where creds.Email == userobj.Email
Do get back in case you need further assistance
All the best,
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward!
We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>