MySQL Bugs: #1490: Need a JDO implementation for the connector that is application server free

Bug #1490	Need a JDO implementation for the connector that is application server free
Submitted:	5 Oct 2003 22:36	Modified:	6 Oct 2003 7:16
Reporter:	Adi Lev	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J	Severity:	S4 (Feature request)
Version:		OS:	NT/UNix/Solaris
Assigned to:		CPU Architecture:	Any

Description:
One of the biggest problem of MySQL is that is not compatible to Oracle.
Using JDO will remove this dependecies a lot.
COnsider building JDO implementation like you build a JDBC connector.
The benefit it remove most of the incompatibilty out of code (sql) and will let you to penetarte easily into Oracle segment.

I came from Sun and I know two factors:
Oracle is against JDO as this will remove the binding to their product
Sun did enter JDO into J2EE as standrd as they are wanting good relation with Orcale. However this partenship stragey don't show in sells!
As a user of Oracle I says it overkill for a lot of application and overcomplicated and overpriced.

So it time to say Orcale, which is the Microsoft of the Dtaabase, that it time is out and JDO is the way to break it!

How to repeat:
You should not request how to repeat for feature!

Suggested fix:
Supply a native JDO connector on your site!

There are quite a few JDO implementation that work with MySQL, both open source (Apacje OJB, for instance) and commercial. The last time I looked at commercial JDO implementations (2 months back), every commercial version supported MySQL.