| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Melvin Davidson <melvin6925(at)gmail(dot)com> |
| Cc: | John Turner <jjturner(at)energi(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>, Ray Cote <rgacote(at)appropriatesolutions(dot)com> |
| Subject: | Re: PostgreSQL Developer Best Practices |
| Date: | 2015-08-25 02:13:57 |
| Message-ID: | 55DBCF65.10500@archidevsys.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 25/08/15 04:26, Joshua D. Drake 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
>
>
I came to the idea of using surrogate primary keys long before I knew
anything about the software on the above list or anything similar!
Cheers,
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CaT | 2015-08-25 02:23:20 | Re: PostgreSQL Developer Best Practices |
| Previous Message | Gavin Flower | 2015-08-25 02:10:59 | Re: PostgreSQL Developer Best Practices |