Customizing methods with different queries but same logic

[dharmar]

Hi All,

I've a C# application which reads data from AS400. In this application I've written nearly some 20 methods to read data from different tables do some calculations and fill up customized collections. Till its fine.

Now we are adding one more new functionality in to our system. The system has to check the type of functionality (old or new) then proceed accordingly.

For this new functionality also we have to read data from the same set of tables and do the same calculations and fill up the same collections. But the only one different is the SELECT queries used for this new functionality will be different.

I don't want to check the funtionality type in all the methods and use queries accordingly.

How easily we can customize this ? (in future we may add some more new functionality too)

Please advice..

Regards,
DHARMA.R

[r035198x]

Hi All,

I've a C# application which reads data from AS400. In this application I've written nearly some 20 methods to read data from different tables do some calculations and fill up customized collections. Till its fine.

Now we are adding one more new functionality in to our system. The system has to check the type of functionality (old or new) then proceed accordingly.

For this new functionality also we have to read data from the same set of tables and do the same calculations and fill up the same collections. But the only one different is the SELECT queries used for this new functionality will be different.

I don't want to check the funtionality type in all the methods and use queries accordingly.

How easily we can customize this ? (in future we may add some more new functionality too)

Please advice..

Regards,
DHARMA.R

Perhaps you did not design the application well initially.
If you had created a DB class that has generic methods for accepting queries as strings and returning the results then adding support for new queries is the same as simply calling the DB class' methods with a different string as a parameter.

[dharmar]

Perhaps you did not design the application well initially.
If you had created a DB class that has generic methods for accepting queries as strings and returning the results then adding support for new queries is the same as simply calling the DB class' methods with a different string as a parameter.

Hi,

Thanks for the comment.

Actually the system is running for decades and we are to change it now. :-)
Is creating a DB class a only way to solve this issue ?

Regards,
DHARMA.R

[r035198x]

Hi,

Thanks for the comment.

Actually the system is running for decades and we are to change it now. :-)
Is creating a DB class a only way to solve this issue ?

Regards,
DHARMA.R

If you want flexibility on the queries that can be executed by the application and require minimal code changes when new queries are introduced then a DB class accepting strings and performing the queries and connections would solve the problem.
Perhaps I'm not getting your question ...