Using LINQ on Table without the primary key.

Question

0.00/5 (No votes)

See more:

C#

Hi,
Is LINQ suitable for tables without primary key? If no then, is it the disadvantage of LINQ?

Posted 27-Mar-13 23:02pm

raj_arenem

Add a Solution

Comments

Ankur^\m/ 28-Mar-13 5:24am

I am interested in knowing why your table doesn't have a primary key?

raj_arenem 28-Mar-13 6:00am

The table just stores the status, either "Fixed" or "Not Fixed" for a particular ID. Like:
MaintainTable->MaintainID, MaintainDetails..., DefectsTable->DefectID, DefectDetails... and the (Table without Primary key) MaintainDefectTable->MaintainID, DefectID, DefectStatus.

I tried to use LINQ, but the values were not getting reflected in the database(MaintainDefectTable). So i arrived at a question, whether LINQ is suitable for such tables.

Thank you.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

J van Rooyen · Answer 1 · 2013-03-27T23:07:00

You would loose a lot of features if you don't utilise primary keys. However, as with ADO and other SQL Data Access Components, the disadvantage is laying in the way the tables are designed - not accessed, in this case.

So, to answer your question - Yes, it is suitable.

However, you will loose a lot of nice features in your case - of my primary concern - is the object model relationships which are automatically handled in LINQ. If you want a similar feature not using LINQ, you would've had to use triggers and stored procedures to handle that kind of 'automatic' hanlding of relationships.