Re: Django models design question

Thank you very much! I choose the first option for now. If I have any problems, I will write them here On Oct 17, 2:51 pm, Stuart wrote: > Hello Omer -- > > I believe you have two options. You could use the AttributeValue > approach I described earlier. You could add

Re: Django models design question

Hello Omer -- I believe you have two options. You could use the AttributeValue approach I described earlier. You could add features to take care of 'data types' and the like. The work may be quite tedious, but it has the advantage of not being clever. In other words, you would do the work to

Re: Django models design question

I should also mention that one AttributeValue table for all the registrations isn't good for my purpose, because it says that the Value column must have a specific type field. I want that every detail (Atrribute) will have the option to be from any field type (CharField,DateTimeField, etc). On

Re: Django models design question

Thank you for the response. As stuart wrote, i should give more details about the website. Currently let's suppose I have 2 interesting tables (I'm not sure that the relationship between these 2 tables is well designed): 1. Details, that contains all the possible information that should be

Re: Django models design question

Hello omerd -- If you give some concrete examples of what you are trying to do, including providing your current models.py code, it will make it easier for us to help you. Since you have Registration and Details models, I am assuming you want the user to be able to create/define these items,

Django models design question

Hello everybody, I am writing my first web application with Django. I want to create a web of registration for many subjects. However, each subject require different set of details to be supplied so I don't know which models should I have in the database. Currently I have two models: