Search Postgresql Archives

Re: Best approach for a "gap-less" sequence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In article <87zme7uvcn.fsf@xxxxxxxxx>,
Jorge Godoy <jgodoy@xxxxxxxxx> writes:

> Harald Fuchs <hf0731x@xxxxxxxxxxxxxx> writes:
>> Why putting gapless numbers into the database at all?  Just calculate them at
>> query time.

> And how would you retrieve the record that corresponds to invoice number
> #16355, for example?  Recalculating few records is fine, but millions of them
> everytime you need to recover some of those is something that doesn't look
> efficient to me... 

This would be

  SELECT whatever
  FROM tbl
  ORDER BY id
  LIMIT 1
  OFFSET 16355 -1

Since id is the primary key, this can use an index scan.



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux