writing update() in the Business Layer {continues with more questions}

petre ricardo

hi,

If code the parameter list as seperate arguments then this wouldnt be a problem, but following a taught pattern that i should take collection as parameters in update or create methods.

Assume the there are three members in a class and in the update or create methods that was told code them to take collection, therefore create and update methods of that class take collection but the problme the caller faces that it doesnt know the order and names of each element of the collection.

Assume :

first element should be Number
second element should be Name
third should be Address

Assume the method signature: public void Update(Dictionary ) but the caller doesnt know that the first element should be Number and the second shold be Name.... therefore if he pass in the wrong order application will fail. How do i indicate to the coder that first element should be Number seocnd Name....?

Is this a good practise?

TY in advance

5 Replies

Know the answer? Post it — somebody with the same question will find it here.

Roei Bar17y ago
Accepted answer
again the issue of List or Dictionery is very bad

multiple arguments are much better

if you want you can build a Typed Parameter and pass it in the UpdateCOmmand

public class ParmamsList
{
   public int ParamA;
   public int ParamB;
   public string ParamC;
}

public void Update(ParmamsList params)
{
}

OK
0
petre ricardo17y ago
OK then, How do i do this using ADo.NET (Never done typed parameters classes in ADO .NET)
0
Joe Dickinson17y ago
I think using the ado.net framework would be a better answer than trying to re-create the wheel.
0
petre ricardo17y ago
The reason i would use collection for parameters, if the members of a class is more than 5, therefore update() will take more than 5 arguements thus give a long method header....
What's the best way to code the method headers to CRUD operation, Collections or seperate Single parameters?

0
Roei Bar17y ago
well my friend, it is not a good practice to work with list based on Update Commands since you will need to defend your ground on any type you are given and check for specif order and many other pointless messing arround.

if you have a typedList like List

public class UpdateParams

public string ParamA;
public string ParamB;

thats better since you will always get a specific type and still you will have the option to work with multiple params and handle multiple instances
0