Re: MySQL and DB2 storage engine for IBM i -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: MySQL and DB2 storage engine for IBM i
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Tue, 21 Dec 2010 10:38:38 -0800 (PST)
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

From: "BButterworth"
The MySQL/Oracle reps. chalked the change up to IBM pulling
the plug on both MySQL and IBMDB2I.

IBM pulling the plug on MySQL? How is that supposed to make sense? I fail to
see the logic in it. As you already alluded, MySQL adds new workloads to IBM i,
which is in IBM's interest. Hindering or disrupting MySQL under IBM i appears
to be in Oracle's interest. At least, that's how I see it.

-Nathan

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.