Re: Advice on Model Structures

2018-08-14 Thread 'dtdave' via Django users
Many thanks On Monday, 13 August 2018 22:44:05 UTC+1, mark wrote: > > dtdave, > > Basically, the model structure is how you indicated. To achieve changing > the content of a select once the page is loaded, you will have to do some > JavaScript magic. Django-select2 will do that for you, and ther

Re: Advice on Model Structures

2018-08-14 Thread 'dtdave' via Django users
Many thanks On Monday, 13 August 2018 17:57:03 UTC+1, Mikhailo Keda wrote: > > Create a 4 models: > 1. Region > 2. County (has a foreign key to Region) > 3. Office (has a foreign key to County) > 4. Employee (has a foreign key to Office) > > organise url by this pattern: > / > > check this exa

Re: Advice on Model Structures

2018-08-13 Thread Mark Phillips
dtdave, Basically, the model structure is how you indicated. To achieve changing the content of a select once the page is loaded, you will have to do some JavaScript magic. Django-select2 will do that for you, and there are other django packages, or you can roll your own if it is not too complicat

Re: Advice on Model Structures

2018-08-13 Thread Mikhailo Keda
Create a 4 models: 1. Region 2. County (has a foreign key to Region) 3. Office (has a foreign key to County) 4. Employee (has a foreign key to Office) organise url by this pattern: / check this example to handle a form - http://django-select2.readthedocs.io/en/latest/extra.html#chained-selec

Advice on Model Structures

2018-08-13 Thread 'dtdave' via Django users
I would like some advice as the best way with dealing with the following model structure. Region Counties Office Employees I would like to show the relevant counties in the relevant regions and then to show the office in that county followed by the employees in that office. In the view end user