R – How flexible is subsonic

componentsinheritancenhibernatesubsonic

I currently use nhibernate but a guy at work has recently gotten me interested in subsonic again. I really prefer a Poco, domain-driven style approach to development and worry about the database later. It looks like this is partially supported using simplerepository. My question is, how flexible is subsonic in how it generates your database ? For example, nhibernate supports all 3 different types of inheritance mappings and components. Components for those of you not familiar w/ NH, let you change how a class is stored in a table. So if you have a customer and address classes, in one situation you store the address in its own table and linked thru a foreign key, in another situation the address can be stored as part of the customer table.

Does subsonic give you these kind of options?

Thanks,
Craig

Best Answer

Does subsonic give you these kind of options?

In a word, no. SubSonic really doesn't have the flexibility of nhibernate, the payoff is that it also doesn't have the complexity or the rather brutal learning curve. If you really need the inheritance mapping flexibility of nhibernate then you won't get it with SubSonic. The only question then is whether you actually need it, I've found I can almost always do without it.

Related Solutions

C++ – How to declare an interface in C++

To expand on the answer by bradtgmurray, you may want to make one exception to the pure virtual method list of your interface by adding a virtual destructor. This allows you to pass pointer ownership to another party without exposing the concrete derived class. The destructor doesn't have to do anything, because the interface doesn't have any concrete members. It might seem contradictory to define a function as both virtual and inline, but trust me - it isn't.

class IDemo
{
    public:
        virtual ~IDemo() {}
        virtual void OverrideMe() = 0;
};

class Parent
{
    public:
        virtual ~Parent();
};

class Child : public Parent, public IDemo
{
    public:
        virtual void OverrideMe()
        {
            //do stuff
        }
};

You don't have to include a body for the virtual destructor - it turns out some compilers have trouble optimizing an empty destructor and you're better off using the default.

How to specify table mappings with Subsonic

SimpleRepository automatically creates the table definitions based on the classes you define so there's no mapping to be done.

Best Answer

Related Solutions

C++ – How to declare an interface in C++

How to specify table mappings with Subsonic

Related Topic