I would guess that it would be MySQL making the majority (all?) of the
changes to support J2EE platforms, not just Orion. To Orion, it's just
another storage mechanism.
As for "why bother?". Well, that's what "open" software is all about.
Open minds, open discussions, open ideas, etc, etc. Some are close-minded
about MySQL, but many happen to like it.
I'm not sure what "fixed in time" has to do with this -- is there some
schedule MySQL has to meet?
I happen to think this discussion is very important from a technical
standpoint and because it's about ideas and attitudes. Besides, a little
venting of frustration now and then is healthy. Sorry for cluttering your
inbox.
Jay
At 07:46 PM 4/18/01 -0400, you wrote:
>
>
>On Wed, 18 Apr 2001, Jay Armstrong wrote:
>
>>
>> But, let's say it doesn't support transactions. What's wrong with starting
>> a dialog?
>>
>Why bother? So the people who bleat about mySQL all the time are
>happier? Frankly I'd rather the Orion team concentrate on functionality
>and J2EE implementation, rather than worry about integrating with MySQL
>when SO many far superior alternatives exist. Have a look at
>config/database-schemas.
>
>In my opinion, Orion should not do ANYTHING to 'conform' to MySQL or adapt
>to it. If MySQL is fixed in time and has a decent JDBC driver that can
>support transactions and all else that is required, then this whole
>ridiculous discussion is moot anyways.
>
>Lets move on now!
>
>Hani
>
>
>
