Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8594155
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T00:08:12+00:00 2026-06-12T00:08:12+00:00

I just today learned a little about Composition over Inheritance . I was wondering

  • 0

I just today learned a little about Composition over Inheritance. I was wondering if I should apply the concept to something I wrote recently.

We previously had two classes that were almost identical, aside from a couple small differences. They contained some basic database access features, but operated on different (but related) object types. So we previously had class that were structured something like this:

class BallMillDBHandler{

    public BallMillDBHandler(){ ... }

    public void InsertTool(BallMill tool) { ... }
    public BallMill QueryTool(string toolID) { ... }
    public void UpdateTool(BallMill tool) { ... }
    public void DeleteTool(string toolID) { ... }
}

class DiamondToolDBHandler{

    public DiamondToolDBHandler(){ ... }

    public void InsertTool(DiamondTool tool) { ... }
    public DiamondTool QueryTool(string toolID) { ... }
    public void UpdateTool(DiamondTool tool) { ... }
    public void DeleteTool(string toolID) { ... }
}

I took the majority of near-duplicated methods and refactored them out into a BaseToolDBHandler() class, and inherited it from the other two, providing a few abstract methods and properties to handle differences in accessing the database parameters themselves.

Would it make sense to make the BaseToolDBHandler a helper class instead, contained within the database accessors, and provide them a common interface the previously abstract properties/methods? Or should I leave it as a case of inheritance?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T00:08:13+00:00Added an answer on June 12, 2026 at 12:08 am

    This looks like a scenario that would benefit both generics and inheritance via a base class / interface.

    class DBHandler<TTool> where TTool : ToolBase // or ITool
    {
        public DBHandler(){ ... }
    
        public void InsertTool(TTool tool) { ... }
        public TTool QueryTool(string toolID) { ... }
        public void UpdateTool(TTool tool) { ... }
        public void DeleteTool(string toolID) { ... }
    }
    

    If you need to, you could make a base (optionally abstract) class, or an interface to use as a type constraint that would guarantee certain members that you needed the tools to have inside the method bodies.

    Examples:

    var handler = new DBHandler<BallMill>();
    BallMill value = handler.QueryTool("xyz");
    value.SomeProperty = "New Value";
    handler.UpdateTool(value);
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've just today learned of asp.net mvc, and I'm wondering what is needed from
I just learned about XLST on stackoverflow today (I love how in computers you
I just learned about .delegate today, and I know I can be used for
I just learned about character sets today, so forgive the newb factor if this
Today we learned about tying the knot in SML where you have something like
I just learned about XSL and XSLT a few days ago and now I'm
Just today learned that one of my websites, TwitPeek.net, is not rendering properly in
We were just today discussing it, so I went on a little search but
I just learned subprocess.check_call() function today. I intend to use it to replace my
Today I just learned that Adobe Air has a local SQL database, which is

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.