I have a stuck in a stored procedure to pass multiple ID parameters, for example, it just feels wrong :
GetMyObject (ListofIDs, OtherParam1, OtherParam2, ...)
How to understand this (if I want it right) .. But I do not feel like I should do it. I think this "mill object" dashes the purpose of the stored procedure / sub-routine. I think that to support the appropriate filter parameters, I should make my SP. If my caller has a list of IDs, should they not call SP often?
Help?
A "Receive Item by ID" should never return more than one object, Because it does not understand language at all.
A "Receive Item by ID" routine? Of course, if you have been used well for it and it will be used quite a lot.
But most of the time, yes, rather than returning many items regularly by ID, you have a regular, which gives items based on application-able filtering parameters (like "I have more than $ 10 from January 8 For all transactions ").
By the way, sometimes there is a limit to the ID (like everything 5 to 10) is a perfectly valid set of filters!
By coincidence, it is not necessary that only one MySQL or SQL-in-common problem is in almost any type of dataset query API in any language, they present these same design questions, and their answers usually But they will be very similar.
Comments
Post a Comment