Geoff, Pedro, Just so you understand my perspective, I've spent a good deal of my career consulting for companies in the Fortune 500. And if TinyERP stays strictly tied to Postrgresql it stands very very little chance of being adopted by any of these companies. And yet these are the companies that spend a great deal on services surrounding their software. I know, I've seen the budgets. I've interfaced with many of the vendors providing maintenance and enhancement services for the enterprise applications for these companies. These companies have well defined database architectures and anyone wanting to introduce new solutions into these environments will have to fit within their existing architectures. And no OFBiz is not an option. It is bloated J2EE overkill and it has almost no real market penetration outside of a few ecommerce sites. Most of us have grown tired of the J2EE/.NET overkill and the mammoth complexity. Anyway, back to database abstraction. I guess the question comes down to where TinyERP sees itself. If it sees itself as only servicing small businesses then being tied to one database is not so bad. But if it sees itself as anything more than this, then being tied to one database will greatly limit the potential market for the software. It is just a fact that if I were to propose an ERP solution tied to postgresql in an enterprise that was Oracle, had all Oracle certified DBA's, had developed hundreds of custom processes and scripts surrounding Oracle, I would stand zero chance of making that sale. And the same is true for other companies that have based themselves on MySQL or SQL Server. And it has nothing to do with how good or bad postgresql may be as a database.
Regards, Gerry Gerry _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
