Why does TableAdapter make "insert " and "select" automatically?

Question

4.00/5 (1 vote)

See more:

I'm not sure why auto-generator make TableAdapter with 'insert' and 'select' command by TableAdapter configuration wizard, if they have any primary keys on VisualStudio2010.

The below code is generated from the wizard.

InsertCommand = INSERT INTO [Table] ([UserID], [Password]) VALUES (@UserID, @Password); SELECT UserID, Password FROM Table WHERE (UserID = @UserID)

I heard it caused concurrency violation Exception if 'select' block is manually removed.

So is it to adjust between DB and TableAdapter?

Any comment is welcome.

Thank you in advance.

Posted 25-Aug-12 1:54am

axt_star

Updated 25-Aug-12 2:00am

v4

Add a Solution

2 solutions

Solution 1

The TableAdapter classes are for people too dumb to write their own code. They have almost no use in real world code, they break every rule of data abstraction. Write your own data layer.

Posted 25-Aug-12 2:04am

Christian Graus

Comments

axt_star 25-Aug-12 9:32am

It's severe opinion. I have no problem with source code.
It's only my curious. So I have no code and only I tried that by VisualStudio.
Anyway, thank you telling me interested matter.

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)

**AmitGajjar** · Accepted Answer · 2012-08-25T03:31:00

Hi,

Specially when people ask me for data Interaction scenario, i prefer SQLHelper class and Stored Procedures. If you would like to follow N-Tier architecture then you can separate you Data Access Layer.

So, i suggest you to create Stored procedure for all your database interactions. Create Transactions if required in the stored procedure. Call your SP from Data Access Layer and Bind it with the real Class object.

Truly speaking i have never used TableAdapter in my projects.

Please refer this : SQL Helper Class[^]

SQL helper class will reduce your work. you can improve that class as per your requirement(but i don't think you need at this stage)

Thanks
-Amit Gajjar.