| From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Developer Best Practices |
| Date: | 2015-08-24 17:19:22 |
| Message-ID: | CANu8Fiz7NSdQzhXqHAY+xQYt07U1Ae13SZNNd8_LunN9Lzg0pQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thank you John R. Pierce. Finally someone who understands the purpose of
this thread. Otherwise, next thing you know, we'll have Web apps/developers
designing bra's for milk cows so they'll look better in the field. :)
On Mon, Aug 24, 2015 at 1:05 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 8/24/2015 9:34 AM, Melvin Davidson wrote:
>
>> And again, I am talking about _database_ design, not Web apps. Letting
>> Web developers design a database to work with their app, is a very, Very,
>> VERY bad idea.
>> It is far better to let DBA's and "database develeopers" design a good
>> database, then to let those apps mold a db into a non-optimum design.
>>
>
> if you let the app drive the database design, you tend to end up with a
> database which is only useful to that single app, and likely breaks when
> that app changes.
>
> --
> john r pierce, recycling bits in santa cruz
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florin Andrei | 2015-08-24 18:41:51 | Re: master/master replication with load balancer in front |
| Previous Message | John R Pierce | 2015-08-24 17:05:42 | Re: PostgreSQL Developer Best Practices |