Databases
StackOverflow2013
Postsdbo
PODjango TastyPie PUT Nested User Model Correctly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango TastyPie PUT Nested User Model Correctly
    primarykey
    data
    text
    <p>I'm trying to go with-the-grain using Django TastyPie to update my models. I have an Identity model, acting as a wrapper around default Django user model:</p> <pre><code>class Identity(ProfileBase): user = models.OneToOneField(User, related_name='identity') avatar = models.ImageField(upload_to=avatar_upload_path, blank=True, null=True) </code></pre> <p>I have my <code>UserResource</code>:</p> <pre><code>class UserResource(ModelResource): class Meta: resource_name = 'user' queryset = User.objects.all() fields = ['email', 'first_name', 'last_name'] include_resource_uri = False </code></pre> <p>And I have my <code>IdentityResource</code>:</p> <pre><code>class IdentityResource(ModelResource): user = fields.ToOneField(UserResource, 'user', full=True) class Meta: resource_name = 'identity' queryset = Identity.objects.select_related() fields = ['user', 'avatar'] always_return_data = True include_resource_uri = False authentication = OAuthTokenAuthentication() authorization = Authorization() </code></pre> <p>I'm currently successfully updating first_name, last_name using the ModelResource <code>obj_update</code> method within <code>IdentityResource</code>:</p> <pre><code>def obj_update(self, bundle, request, **kwargs): print 'updating object' bundle = self.full_hydrate(bundle) bundle.obj.user = request.user user = bundle.data['user'] bundle.obj.user.first_name = user['first_name'] bundle.obj.user.last_name = user['last_name'] return super(IdentityResource, self).obj_update(bundle, request, user=request.user) </code></pre> <p><strong>I want to make a <code>PUT</code> request and optionally update any field on the user or identity models (first_name, last_name on user, or the avatar field on identity).</strong> I would rather not have to manually access each field from the bundle data and set them on models manually, as I have done above. </p> <p>How can I do this naturally in TastyPie? Can someone explain a better approach to solving this problem? Any direction is GREATLY appreciated. :)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkyleturner
    1. USkyleturner
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango TastyPie PUT Nested User Model Correctly
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango TastyPie PUT Nested User Model Correctly
      1. USTadeck
      1. VTFavorite
    3. VO
      singulars
      1. PODjango TastyPie PUT Nested User Model Correctly
      1. USTadeck
      1. VTBountyStart
    1. COI have set a bounty, so the question hopefully will gain more attention and someone will provide the answer that could be then treated as canonical (hopefully). Many people were hitting similar problem, as this is standard practice in Django to handle user information extensions that way (by adding new model in relation one-to-one to User model). People just need to remember about one additional thing: the signal that is usually used with this solution and automatically creates Identity / UserProfile instance assigned to User instance.
      singulars
      1. PODjango TastyPie PUT Nested User Model Correctly
      1. USTadeck
    2. COIsnt creating a User from a relation like this risky? How would you setup Passwords and notify them? I would stay away from writing generic solutions like that because they can lead to security issues downstream.
      singulars
      1. PODjango TastyPie PUT Nested User Model Correctly
      1. USfundamol
    3. COIt looks like you are updating currently logged in user. Is that on purpose? I doubt it.
      singulars
      1. PODjango TastyPie PUT Nested User Model Correctly
      1. USTadeck
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload