about 2.5.10 // Resolved 0002294: DB gets corrupted after schema change

[Erne]

On 23-apr-07, at 10:58, Ruslan Zasukhin wrote:

> On 23/4/07 11:41 AM, "Erne" <ernestogiannotta at tiscalinet.it> wrote:
>
> Hi Erne,
>
>>> About 2.5.10
>>>
>>> We now put 200% of efforts to ship 3.0 release asap.
>>>
>>> Yes we have start process of bug review and fixes.
>>> They go now into main branch of 3.0.
>>>
>>> Very unlikely we will get 2.5.10
>>>
>>
>> mmm... wouldn't it be nice to have some reliably stable 2.5.x as
>> solid ground for 3.0?
>
> We will consider this of course.
> But time ...
>

Let's hope :-)

>> This is a quite annoying bug that can affect anyone trying to update
>> a db schema.
>
> No, 3.0 is not so painful as switch to 2.1.
>
> If you open db by 3.0 engine, it only add dummy records about  
> Triggers,
> Views, ... Into SYS tables. This NOT change FORMAT of db. So engine  
> 2.x can
> open this db also again.


Well, this is good to hear.

I was talking about bug 0002294 though, which is a nasty one  
corrupting a DB when changing some indexed method field definition  
and makes 2.5.9 a not so reliable release

Cool Runnings,
Erne.

/ |\ |\  | /
– |/ | \ | –
\ |\ |  \| \