> -----Original Message-----
> From: Vladislav.Vaintroub@stripped [mailto:Vladislav.Vaintroub@stripped]
> On Behalf Of Vladislav Vaintroub
> Sent: Friday, January 30, 2009 2:50 PM
> To: 'Philip Stoev'; 'FalconDev'
> Subject: RE: NULLs and stuff
>
>
>
> > -----Original Message-----
> > From: Philip.Stoev@stripped [mailto:Philip.Stoev@stripped] On Behalf Of
> > Philip Stoev
> > Sent: Friday, January 30, 2009 2:46 PM
> > To: 'FalconDev'
> > Subject: Re: NULLs and stuff
> >
> >
> > Correct me if I am wrong, however Jim's design allows for a database
> > version
> > counter that we can increment in order to handle older tablespaces
> the
> > way
> > we handled them previously and handle new tablespaces the new way.
>
> Maybe , but my point is not to do it, even if possibility is there.
> After
> release, we need to handle backward compatibility. Before release, we
> do
> not.
OTOH, I see no harm if we increment this version counter and disallow
incompatible databases to start. I just want to avoid any form of automatic
conversion, manual dump in old version/ recreate in new version should
work.
