in reply to Re^2: Architecture design for full stack development.
in thread Architecture design for full stack development.

Hello, I would strongly disagree with the last statement, that is is OK to reuse value of a primary key. Such approach invalidates any attempt to compare previous state and current state of a record in a table (since meaning of the id value is changed). Of course, this sentiment is probably irrelevant to the problem you are trying to solve...
  • Comment on Re^3: Architecture design for full stack development.

Replies are listed 'Best First'.
Re^4: Architecture design for full stack development.
by chacham (Prior) on Jun 26, 2017 at 20:32 UTC

    Such approach invalidates any attempt to compare previous state and current state of a record in a table

    If a previous value has meaning, it should never have been deleted. Also, in most schemes, PK re-use come some time after its original use.

[reply]

In Section Seekers of Perl Wisdom