Good clarification.  Any downside to using an auto increment number?

```````````
 fiKeyID INTEGER GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY
```````````

On Fri, Dec 13, 2019 at 12:15 PM Mark Rotteveel m...@lawinegevaar.nl
[firebird-support] <firebird-support@yahoogroups.com> wrote:

>
>
> On 13/12/2019 19:07, Clyde Eisenbeis cte...@gmail.com [firebird-support]
> wrote:
> > Is <timestamp> a field I create, or is it part of all records?
>
> It is a field you create. Which is why I wrote "Where <table> is the
> table in question, and <timestamp> is a suitable column (eg a timestamp)
> to determine what the newest record is."
>
> You might be able to use the pseudo-column RDB$RECORD_VERSION, but that
> is not necessarily in the right order of recency, because the value is
> the transaction-number that wrote the last version of the record. This
> means that updates to a record will also make it 'recent' and a record
> written by a long-running transaction might not show up as 'recent' (or
> at least as older than it may actually be).
>
> Mark
> --
> Mark Rotteveel
> 
>
  • Re: [fir... 'Marcin Bury' marcin.b...@studio-delfi.pl [firebird-support]
    • Re:... Clyde Eisenbeis cte...@gmail.com [firebird-support]
      • ... Kjell Rilbe kjell.ri...@marknadsinformation.se [firebird-support]
        • ... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
          • ... Clyde Eisenbeis cte...@gmail.com [firebird-support]
            • ... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
              • ... Clyde Eisenbeis cte...@gmail.com [firebird-support]
              • ... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
              • ... Clyde Eisenbeis cte...@gmail.com [firebird-support]
              • ... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
              • ... Clyde Eisenbeis cte...@gmail.com [firebird-support]
  • Re: [fir... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]

Reply via email to