Actually abstracting your database would look like taking the lowest common denominator and assuming your database can only support that. Unless you're buildin

Actually abstracting your database would look like taking the lowest common denominator and assuming your database can only support that. Unless you're building a piece of software where database agnosticism is actually a required feature, then I generally find it to be a very poor tradeoff. Databases are incredibly powerful, you should be using them to their fullest extent rather than purposefully handicapping yourself.