[Info-vax] Other than Oracle, What MySQL/DBMS options are there for OpenVms?
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Tue Mar 26 14:46:20 EDT 2019
Den 2019-03-26 kl. 19:26, skrev Arne Vajhøj:
> On 3/26/2019 1:56 PM, Dave Froble wrote:
>> On 3/26/2019 8:02 AM, Arne Vajhøj wrote:
>>> On 3/26/2019 1:48 AM, Phillip Helbig (undress to reply) wrote:
>>>> In article <q7c2f5$1jmf$1 at gioia.aioe.org>, =?UTF-8?Q?Arne_Vajh=c3=b8j?=
>>>> <arne at vajhoej.dk> writes:
>>>>> Version number wise RDB has taken 23 years to go from 7.0 to 7.3.
>
>> Short term memory fails you.
>>
>> Some may remember the spat between HP and Oracle, and something from
>> Oracle about new versions and support and such. Now, it was, I seem to
>> recall, about Oracle Classic on HP-UX, mainly. The Rdb people avoided
>> any issues by just not using certain numbers in versions. They could
>> implement any new features they wished, they were just limited in what
>> they could call them.
>>
>> Don't be so quick to forget the past.
>
> ????
>
> As I remember the HP Oracle dispute then:
> * Oracle announced they would stop supporting Itanium
> * HP sued because they believed Oracle was contractually bound
> to support Itanium
> * The judge agreed with HP
>
> I do not remember anything about Oracle not being allowed to
> bump major version numbers.
>
> Arne
Well, Oracle planned to issue a "last version" list for their VMS
Itanium products. The Rdb team had a new Rdb version nearly finished.
They released it to a few selected customers, just to be able to add
"7.3" to that list. And after that, they had to stick with the 7.3.x.x
line of versions to not break against that "last version" list, they
were not allowed to release a 7.4 or, for that matter, an 8.0 version.
This is how the Rdb team presented this on some customer forum.
Since you're not updated on the background here, you do not know this.
More information about the Info-vax
mailing list