List:Falcon Storage Engine« Previous MessageNext Message »
From:Vladislav Vaintroub Date:February 16 2009 10:25pm
Subject:RE: Patch for bug#42208
View as plain text  

> -----Original Message-----
> From: Jim Starkey [mailto:jstarkey@stripped]
> Sent: Monday, February 16, 2009 11:08 PM
> To: Vladislav Vaintroub
> Cc: Lars-Erik.Bjork@stripped; 'FalconDev'
> Subject: Re: Patch for bug#42208
> >
> Wrong!  You need to bump the minor version number and create new
> indexes
> using a new index version number.  This means:
> 
>     * Old versions of Falcon will error on opening new databases.
>     * New versions of Falcon will honor the previous index formats
> 
> When a new version of the software opens an old database, it should
> bump
> the minor version number (it only really needs to do this if it creates
> a new index).

Jim, INDEX_VERSION_1 is already cluttering the codebase enough, so I prefer
not to propose INDEX_VERSION_3 now:) Falcon is alpha, people can dump and
reload the database when upgrading until we reached release and this should
change once we reached the release. I do not know of any software product
that will support "alpha" formats. 
And even when we reached the release also then, INDEX_VERSION in my opinion
should be an only indicator for upgrade utility and multiple versions should
not clutter the codebase (except the upgrade utility which is allowed to be
messy) and should not clutter the rest of the codebase.

Of course all this is just my personal opinion, but it is based on years
designing and maintaining upgrade utilities of another database product:)



Thread
Patch for bug#42208Lars-Erik Bjørk16 Feb
  • RE: Patch for bug#42208Vladislav Vaintroub16 Feb
    • RE: Patch for bug#42208Vladislav Vaintroub16 Feb
      • Re: Patch for bug#42208Jim Starkey16 Feb
        • RE: Patch for bug#42208Vladislav Vaintroub16 Feb
    • Re: Patch for bug#42208Jim Starkey16 Feb
      • RE: Patch for bug#42208Vladislav Vaintroub16 Feb
      • Re: Patch for bug#42208Lars-Erik Bjørk17 Feb
        • Re: Patch for bug#42208Kevin Lewis17 Feb
          • Re: Patch for bug#42208Ann W. Harrison18 Feb
            • Re: Patch for bug#42208Ann W. Harrison18 Feb
              • Re: Patch for bug#42208Ann W. Harrison18 Feb
                • Re: Patch for bug#42208Kevin Lewis18 Feb
                  • Re: Patch for bug#42208Ann W. Harrison18 Feb
                    • Re: Patch for bug#42208Kevin Lewis18 Feb
          • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
            • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
              • Re: Patch for bug#42208Kevin Lewis18 Feb
                • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
                  • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
              • Re: Patch for bug#42208Jim Starkey18 Feb
                • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
                  • Re: Patch for bug#42208Jim Starkey18 Feb
                    • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
                      • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
            • Re: Patch for bug#42208Ann W. Harrison18 Feb
              • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
                • Re: Patch for bug#42208Jim Starkey18 Feb
                  • Re: Patch for bug#42208Ann W. Harrison18 Feb
                    • Re: Patch for bug#42208Ann W. Harrison18 Feb
                • Re: Patch for bug#42208Ann W. Harrison18 Feb
                  • RE: Patch for bug#42208Vladislav Vaintroub18 Feb
                    • Re: Patch for bug#42208Ann W. Harrison18 Feb
                    • Re: Patch for bug#42208Kevin Lewis18 Feb
                      • Re: Patch for bug#42208Ann W. Harrison18 Feb
      • Re: Patch for bug#42208MARK CALLAGHAN17 Feb
  • Re: Patch for bug#42208Jim Starkey16 Feb