Is it really necessary to have a different class for postgres than for MySQL?

[jeroarenas]

The problem of having to classes, one for mysql and another for postgres is that changes done in one of them should be migrated to the other. One ends up having two different classes with many functions in common.

Would it be feasible to have a parent class with common functions, and then inherit with two different classes ?

Priority of this issue is low ... we need to discuss when and if this is implemented at all