Thx Daniel

El mar., 6 ago. 2019 a las 19:28, Ronaldo Mata (<[email protected]>)
escribió:

> I think they do that using ajax, but I would like to know how to do it in
> the best way, and if it is necessary to create additional models for make
> and model, and relate them to Car
>
> El mar., 6 ago. 2019 a las 19:26, Ronaldo Mata (<[email protected]>)
> escribió:
>
>> I am basic in web development, but I would like to generate something
>> like here:
>> https://www.cargurus.com/
>>
>> When I select a make, the options for the model are automatically
>> updated, that is, when I select a make, the model input only shows the
>> models associated with that make.
>>
>> El mar., 6 ago. 2019 a las 19:04, DANIEL URBANO DE LA RUA (<
>> [email protected]>) escribió:
>>
>>> If you use the same name for three values you will have a array on the
>>> get or post then you have to no the order
>>> And for the filter use filters from your model to get the right car if
>>> that what you need ;)
>>>
>>> On Wed, 7 Aug 2019, 01:00 Ronaldo Mata <[email protected] wrote:
>>>
>>>> Hello! I would like you to help me implement a filter form, I put them
>>>> in cotexts:
>>>>
>>>> Example:
>>>> I have a website about cars, I created my Car model with attributes
>>>> such as:
>>>> - colour
>>>> - make
>>>> - model
>>>> - price
>>>>
>>>> Now I want to find a way to make a filtering using a form, the case is
>>>> that the form will have three input type drop-down, [make, model, price],
>>>> when the user selects a make the model input must display only the models
>>>> available for that make, how to achieve that?
>>>>
>>>> Is it necessary to implement a Make and Model model and associate them
>>>> with Car by a foreign key?
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Django users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/django-users/CAP%3DoziTmabU-O0GmSZUr-BUWkYHzuFCLV1zyO4t-2b4NqCcZMw%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/django-users/CAP%3DoziTmabU-O0GmSZUr-BUWkYHzuFCLV1zyO4t-2b4NqCcZMw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/CAO_yRT2y9tCcJDR0sjwCkcFWSJyr3cJnPc%3DEPesCbqx95ut%3DzA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/django-users/CAO_yRT2y9tCcJDR0sjwCkcFWSJyr3cJnPc%3DEPesCbqx95ut%3DzA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAP%3DoziQ0phpg7i-XrS%3DhwrFj5gff2vp9REGstfE677az4Hb1GA%40mail.gmail.com.

Reply via email to