Sending data to database
-
I have a class and the data in it has to be stored in the database. I have done this by extracting every single property and sending each of them as input parameters to a stored procedure in the database. But the thing is that the class has too many properties. Is there any way to accomplish this in a single go(lesser amount of code)? OH and I am using C# and Sql Server!
-
I have a class and the data in it has to be stored in the database. I have done this by extracting every single property and sending each of them as input parameters to a stored procedure in the database. But the thing is that the class has too many properties. Is there any way to accomplish this in a single go(lesser amount of code)? OH and I am using C# and Sql Server!
Presumably it throws an exception and posting that exception as part of your post is helpful. Presuming that the exception is telling you the statement is too big... If your SQL statement is too long then SQL/C# will have a problem with it. The solution is to reduce the size. (Might note that that could indicate a database design issue as well.) Using the database import tools (sqlldr?) might help with the problem but might not. If not or you don't want to use it then solutions. 1. Do two calls. 2. Pass in a blob and parse it to create dynamic sql. If it was me I would presume that there is a design issue.
-
I have a class and the data in it has to be stored in the database. I have done this by extracting every single property and sending each of them as input parameters to a stored procedure in the database. But the thing is that the class has too many properties. Is there any way to accomplish this in a single go(lesser amount of code)? OH and I am using C# and Sql Server!
As has been mentioned, if the table has too many field then there is probably a design problem. Communication with the database is donkey work, most developers use or write a code generator for this. I have not hand coded DAL for many years.
Never underestimate the power of human stupidity RAH
-
As has been mentioned, if the table has too many field then there is probably a design problem. Communication with the database is donkey work, most developers use or write a code generator for this. I have not hand coded DAL for many years.
Never underestimate the power of human stupidity RAH
The thing is I am still new. Is it not good that we do more of the grunt work at the starting stages itself? And DAL coding is quite hectic. Sometimes I really feel why do we need it anyway. Thank you for eye opener atleast.