Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Question about DRF serializers. Especially ModelSerializer.
There are two versions with Foreign Key:
field = CharField(source='user.name')
field = SeriaizerMethodField()
get_field(self, obj):
return obj.user.name
What will work better / quickly ?
UPD
yes, I know about select/prefetch_related.
But is better just to pull required field from database and serialized it automaticaly or pull some 'raw' fields and nicely join them in serializer?
There are no difference between them. If you want to improve speed you should do it in a view by calling select_related method of a queryset.
YourModel.objects.select_related('user')
It'll join user table and calling user.name atribute will not hit a database next time
First one provides different validation options from the box. While the second one is something very customizable and doesn't provide any validation itself.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 months ago.
Improve this question
Can you please provide an example of views.py for updating(or creating) fields without using forms.py?
Here you go.
Please, next time, do some research.
Just searching "django update or create" will give you a very nice django doc to the queryset method.
obj, created = Person.objects.update_or_create(
first_name='John', last_name='Lennon',
defaults={'first_name': 'Bob'},
)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
i've a question and need your help
i have a empty form with about 10 input fields. all i want to do is :
if a user fill in the user's login name and hit the tab key - the other fields should be filled out with the related data stored in the database. like users location, email etc.
could some give me a cfml related example please?
Here is how to approach this:
Use javascript to check for on tab event ( key press for the tab key )
Call a cfc, passing the value of the input field to the cfc
query the database for a field that matched exactly that data
return the data as json and populate the rest of the fields.
Assuming you have basic javascript and cfml skills this would be the way I would approach this.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I'm trying to customize Sales 365. I need a field in a Lead form to multiselect items from Account View.
Is there any way to do it without coding?
Thanks
You can't have a field but you can have a subgrid, relationship between Lead and Account will be N:N, in this way the user can select multiple records from the Account entity.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I want to create a form that does the following: the user specifies the number of questions that they want to ask and then on the next page, the user is able to fill out the relevant details pertaining to the number of questions that they to ask. I was wondering if there is a simple way to do this using django forms?
My approach is as follows:
I use one form to record the number of questions that the user wants to ask with a general description, then when the user clicks submit/next, the next view would create a form with those number of questions; however, I'm running into a complication when trying to use this method. I want to link the first form to the second form, but not sure how to because I can't preserve any information in the view from each call.
Is there a better way of going about this problem?
You certainly can preserve information between views. Perhaps the easiest way to do this is in URL parameters; your first view can redirect to "/second_view/?number_of_questions=5" and the second view can access request.GET['number_of_questions'].
An alternative, which is particularly useful if you have a lot of data, would be to use the session; add the data to the session on submit in the first view, and pop it out in the second.
In Django 1.8, the django.contrib.formtools module was moved into a separate package, django-formtools. It includes the FormWizard, which is the standard tool you'd use to create a form that spans multiple pages and/or steps.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I want to dynamically change the required attribute on form fields. The reason for doing this is because a user can select "Same address as previous user" yes/no.
If yes then it hides the fields on the frontend and I would want to make the fields which are required by default not required when validating / processing the modelform.
Here is a very nice discussion of this topic in general: Dynamic form requirements in Django .
If you just want to do something really simple, there are two very basic ways that I can think of:
Set the field to not be required and use a custom clean function to check that it exists when it should exist. (If you want an asterisk to appear after the field title, just use some simple javascript.)
Have two different forms--one with the field required and one without--and use javascript to display the correct form.
The first solution is obviously much simpler for exactly what you asked, but if you want to do something even slightly more complicated, you might prefer the second option.