Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 2
    "And it's also worth remembering that the database engine can't enforce transactional consistency with people's brains, with paper records, with cached displays of data..." --- definitely this point helps. What you get from the database is a snapshot of the state of the system at a given point in time, not a guarantee that it represents reality. This is a hard change in perspective that @Alessandro will need to become accustomed to. Commented Feb 14, 2024 at 15:13
  • 2
    @GregBurghardt, I'd put the same point in slightly different terminology: you get a snapshot of the business records stored in that application. A number of relevant points for the OP are: (a) lots of business information is not recorded but exists only in the knowledge of human actors and decision-makers (who can talk/act directly), (b) if information is recorded, it often cannot be recorded instantaneously with the event the record is about, and (c) businesses ordinarily have more than one place for storing records which are not all fully centralised, nor fully consistent at all moments. Commented Feb 14, 2024 at 15:54