OOP中的数据库查询...设计模式？(Database queries in OOP… design pattern?)

 这是基本问题。 假设我有一个基类Foo。 此类调用数据库以获取要在类中缓存的一些数据。 
 
public class Foo
{
    // Properties/fields go here.

    public virtual void ReadData()
    {
        // Queries the database for information and stores it in Foo.
    }
}
 
 现在，假设我有一个名为Bar的派生类。 这个类想要缓存一些额外的数据。 
 
public class Bar : Foo
{
    // Additional properties/fields go here.

    public override void ReadData()
    {
        base.ReadData();

        // Queries the database for additional information and stores it in Bar.
    }
} 
 
 现在，看看这个，如果你做普通的OOP，似乎有点常见。 但是，在这种情况下，您访问数据库两次效率低下。 我正在开发一个遗留代码库，可以在所有地方执行此类操作。 在下一个版本中，他们希望数据库访问优化（意味着，更少调用DB）。 
 
 是否存在可与OOP一起使用的数据库访问设计模式，以便最大限度地减少数据库上的查询量？ 

This is the basic problem. Say I have a base class Foo. This class does a call to the database to get some data to cache in the class.
 
public class Foo
{
    // Properties/fields go here.

    public virtual void ReadData()
    {
        // Queries the database for information and stores it in Foo.
    }
}
 
Now, say I have a derived class called Bar. This class wants to cache some additional data.
 
public class Bar : Foo
{
    // Additional properties/fields go here.

    public override void ReadData()
    {
        base.ReadData();

        // Queries the database for additional information and stores it in Bar.
    }
} 
 
Now, looking at this, it seems like a somewhat common thing to do if you were doing regular OOP. But, in this case, you are accessing the database twice which is inefficient. I'm working on a legacy codebase that does practices like this all over the place. In the next release, they want database access optimization (meaning, less calls to the DB).
 
Is there a design pattern for database access that would work with OOP so I can minimize the amount of queries on the DB?

原文：https://stackoverflow.com/questions/20707110