Re: PostgreSQL Developer Best Practices

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.

On Mon, Aug 24, 2015 at 12:26 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:

> On 08/24/2015 08:56 AM, Melvin Davidson wrote:
>
>> >The "serial" key is the default primary key amongst every single web
>> development environment in existence.
>>
>> Methinks thou doest take too much for granted.
>>
>> Yes, serial has it's purpose, but I sincerely doubt it is "the default
>> primary key amongst every single web development environment in existence"
>> I am not sure where you get your stats from. Probably you are referring
>> to "Ruby on Rails". IMHO,
>>
>
> Rails
> Anything that uses Hibernate (Java)
> Django
> Every PHP framework
> Pyramid
> Anything that uses sql-alchemy
>
> I can go on for miles with this. It is true that a lot of these support
> non-serial keys. It is also true that is not the default.
>
>
> JD
>
>
> --
> Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
> PostgreSQL Centered full stack support, consulting and development.
> Announcing "I'm offended" is basically telling the world you can't
> control your own emotions, so everyone else should do it for you.
>

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.