| bio | website | manavgoel.net |
|---|---|---|
| location | India | |
| age | ||
| visits | member for | 1 year, 8 months |
| seen | 2 days ago | |
| stats | profile views | 29 |
I am a freelance developer with specialisation in python web application.
|
May 22 |
comment |
Usage of foreign key when the referenced table data will not change Thanks for the answer. What are these option1 and 2 tables? |
|
May 22 |
asked | Usage of foreign key when the referenced table data will not change |
|
May 16 |
awarded | Notable Question |
|
Dec 9 |
accepted | Postgres Backup queries on AWS after reading Postgres docs |
|
Dec 3 |
comment |
Many To Many Relationships Agreed, it depends on the use case. I just mentioned it so that op gets a clear picture of this type of relationship. :) |
|
Dec 3 |
comment |
Many To Many Relationships Also both the foreign keys should be part of primary key so that no record gets duplicated and it also helps performance when getting data back. |
|
Dec 3 |
comment |
Postgres Backup queries on AWS after reading Postgres docs Regarding pg_start_backup command, I should issue it then take snapshot and then issue pg_stop_backup. Right? |
|
Dec 2 |
accepted | Database design with different user roles connected by different relationships to one organizaiton table |
|
Dec 2 |
asked | Postgres Backup queries on AWS after reading Postgres docs |
|
Nov 19 |
comment |
Moving postgresql data to different drive Thanks. To change directory I just needed to run postgres -D /location after following steps mentioned by you. :) |
|
Nov 19 |
accepted | Moving postgresql data to different drive |
|
Nov 19 |
awarded | Commentator |
|
Nov 19 |
comment |
Moving postgresql data to different drive In 4th point, what do you mean by 'This is usually defined through a commandline parameter...'? |
|
Nov 19 |
asked | Moving postgresql data to different drive |
|
Nov 8 |
awarded | Popular Question |
|
Oct 23 |
comment |
Database design with different user roles connected by different relationships to one organizaiton table I also thought of the same schema which you have mentioned initially. It seems it is the best way. What I am thinking is make Primary_key(user_id, organization_id, employee_type_id). I have to keep a check in application code if an user is already fulltimeemployee then he cannot be connected to any other company. |
|
Oct 22 |
asked | Database design with different user roles connected by different relationships to one organizaiton table |
|
Oct 3 |
accepted | One address table for many types of addresses |
|
Sep 22 |
comment |
One address table for many types of addresses I have two different tables and both need an address. Is it okay if I enter foreign key to address table from both the tables above? |
|
Sep 22 |
revised |
One address table for many types of addresses added 2 characters in body |