On Wed, Feb 4, 2009 at 2:38 PM, Monty Taylor <[email protected]> wrote:
> > So, with NDB (2) is true by default, but it's a terrible config. In a > good config, gaps exist because batches of autoincrement values are pulled. > > I'd like to see (1) go away through config too... I see absolutely no > reason why I shouldn't be able to set autoincrement_increment = -1 and > have it work. > > One of the other use-cases for them doesn't care about either 1 or 2, > but they don't break anything - and that's the "give me a cheap unique > id whos value has no meaning" case. > > I think that by default, most people expect 1 and 2 to be true, but I > think that's mostly habit. And for the sake of migration and less confusion, I lean toward "make a similar but different type" so that auto-increment can simply be auto-increment. The new auto-increment can have different assumptions and constraints and people will understand what they're getting into--at least some will. :-) Jeremy
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
