Re: Rationale for aversion to the central database?

From: Ray Cote <rgacote(at)appropriatesolutions(dot)com>
To: Guyren Howe <guyren(at)gmail(dot)com>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Rationale for aversion to the central database?
Date: 2018-04-09 13:45:34
Message-ID: CAG5tnzqN1mQTFpg7Cs79y1vFAhnBNGDVWC9OgnpmYzYd8akSDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Maintaining your database logic in version control and versioning the
deployed code can be a bit problematic.

Conversely, providing a standardized pgsql module through which data is
updated and retrieved can help standardize access logic across multiple
languages and libraries.

And I concur that database portability is a thing people like to discuss,
but rarely occurs.
Portability is important for general ORM tools, less so for corporate
projects (there are always exceptions).

Like any tool, needs to be used wisely.
I've worked on a project that has 10s of thousands of lines of business
logic in the database and it makes perfect sense for that environment.
--Ray

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Poty 2018-04-09 13:46:52 algo for canceling a deadlocked transaction
Previous Message Peter J. Holzer 2018-04-09 13:44:51 Re: Rationale for aversion to the central database?