Using SQL server views in LINQ

Question

I have a set of SQL server views working as abstraction layer for an underlying table structure. The views are simple abstractions of the underlying tables (renaming of columns and tables) and it is in general possible to edit data using them.

Regardless if I import them in a LINQ to SQL data context or into the ADO.NET Entity Framework, the import process ignores details such as primary keys, identities or required fields of the underlying tables and generates the wrong code for data manipulations. I can repair this by editing the related properties in the designer, but a data structure update later and my changes are gone. I’m searching for a more maintainable method of doing this. Something like adding the missing key and type information to the views, giving LINQ the information to generate the appropriate code. Any recommendations?

Do you do more than just rename the columns and tables? you can do these things using the objects generated in the designer. — 4imble
– 4imble, Commented Dec 13, 2010 at 14:39
I know, but this question is about importing views without editing anything in the designer. — Dirk Brockhaus
– Dirk Brockhaus, Commented Dec 13, 2010 at 14:50

TomTom · Accepted Answer · 2010-12-13 10:09:15Z

1

Ah - not use EntityFramework import tools? Thsoe are IMHO anyway pretty unusable for larger projects (more than 30-50 tables) as it really gets out of hands with its import times etc.

Maintain your mappings in code.

answered Dec 13, 2010 at 10:09

TomTom

62.4k11 gold badges95 silver badges152 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Ian Nelson · Accepted Answer · 2010-12-13 14:18:48Z

0

Have you looked at the ADO.NET Entity Framework ?

edited Dec 13, 2010 at 14:18

Ian Nelson

59.1k20 gold badges79 silver badges104 bronze badges

answered Dec 13, 2010 at 10:10

Dean Chalk

20.5k6 gold badges66 silver badges95 bronze badges

1 Comment

Dirk Brockhaus Over a year ago

I looked at both: LINQ to SQL and LINQ to entities. The missing details are different, but for example neither of them correctly imports the primary keys.

Collectives™ on Stack Overflow

Using SQL server views in LINQ

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related