> Be aware that mySQL will sometimes forget to do the right thing, and that
> PostgreSQL is the reference database AFAICT, so draw your own conclusions if
> its a tossup for you.
Actually, PostgreSQL is "the reference database" only where OFBiz is concerned. OFBiz seems to
have been developed and tested mostly with PostgreSQL, and hardly with other RDBMSs. If you're
using anything other than PostgreSQL with OFBiz, be prepared to do some small bugfixes yourself
(bugs here are RARE, though).
PostgreSQL has many non-standard features, or advanced features rather. Certainly more powerful
than most RDBMSs out there.
That said, RDBMSs are still software created by humans. Every software has bugs here and there.
If there is any problem at all with the data layer aspect of OFBiz, it's not a problem with any
RDBMS, AFAICT. There is one tiny (but significant) bit of a problem in the DBCP, which I
reproduced, documented and fixed. However, the fix may be considered "non-standard or
non-reference" here, so I'm not too keen to debate my fix into OFBiz SVN.
Jonathon
Walter Vaughan wrote:
> Adrian Crum wrote:
>
>> Webtools->XML Import/Export
>>
>> Kenneth Porter wrote:
>>
>>> I know that ofbiz comes bundled with Derby, and that ofbiz can be
>>> used with most DB's that include a JDBC connector. Are there any
>>> tools for moving data between different back ends? For example, how
>>> would one move an existing DB from Derby to MySQL or PostgreSQL?
>
> Also, if mySQL is your first choice make sure you are using latest
> 5.0.xx version and you have your database setup to use the INNODB
> database engine. Be aware that mySQL will sometimes forget to do the
> right thing, and that PostgreSQL is the reference database AFAICT, so
> draw your own conclusions if its a tossup for you.
>
> YMMV
>
> --
> Walter
>
>
Locked
