Timeline for Will table inheritance in PostgreSql suit this situation?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2015 at 11:39 | comment | added | ypercubeᵀᴹ | This is an old question so now (that we have 9.4 and soon 9.5) that "9.2 ONLY" is not entirely clear. Does it mean "9.2 ONLY"" or any later version as well ("9.2+"*)? | |
| Mar 22, 2013 at 8:09 | vote | accept | Lee337 | ||
| Mar 22, 2013 at 0:56 | history | edited | Chris Travers | CC BY-SA 3.0 |
added 1726 characters in body
|
| Mar 21, 2013 at 18:59 | comment | added | Lee337 | Yes, I was thinking about creating a bigint/guid sequence that will serve as a PK. However, I wasn't sure of the repercussions involved with PK's and FK's. If I had to create a few tables, Users, Roles, and a mapping table UserRoles. It would be, Users has has many UserRoles, and Roles has many UserRoles, which will create 2 FK's on UserRoles to Users and Roles. Can you advise me as to how this SHOULD be done with table inheritance? | |
| Mar 21, 2013 at 11:56 | history | migrated | from stackoverflow.com (revisions) | ||
| Mar 21, 2013 at 2:55 | history | answered | Chris Travers | CC BY-SA 3.0 |