Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Where possible avoid simply using id as the primary identifier for the table.

I've found the opposite true in my limited experience, at least when doing any sort of ORM, then having id implicitly as the primary key makes life so much easier.



Old school SQL gurus will tell you the ORM is wrong and just to override it. It breaks USING


Exactly, USING shines when IDs are employee_id or task_id in every table.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: