> > > Don't forget the other two limits that might come into play with
> > > a very large database:
> > >
> > > maximum of 4 billion rows per table
> >
> >This is very interesting for all those wanting to use Int64 as
> their primary
> >keys.
> >This must be the absolute range of Int32. Surely with FB1.5, the maximum
> >rows per table is equivalent to the absolute range of Int64???
> Anyone know?
>
> Internally the engine uses a four byte record identifier, so yes,
> the limit
> is 4,294,967,295 rows. Record identifiers aren't completely dense, so you
> won't get quite that many. They are reused, so you're not
> penalized for deleted
> records.
>
> That restriction will probably be lifted in V2.
>
>
> Regards,
>
>
> Ann

Thanks Ann,
Hopefully my Int64 PKs won't get past 4 billion by the time V2 comes out :-)
But it says something to those who are using UUIDs as PKs - thinking that it
gives them limitless keys for a 1000 years.
Alan