Actually, I was calling listener for *user* object So I needed the update
*user* object. Currently, I have fetched the user object again( after
saving member object) by calling User.objects.get(id=m.user_id)
On Tue, Sep 4, 2018 at 11:47 PM, Adam Johnson wrote:
> Correct, refresh_from_db() is exp
Correct, refresh_from_db() is expected to only update the current model,
not traverse to others linking it (which could be *many*). You'd want
m.refresh_from_db() to refresh the fact that the user field on m has
changed.
On Sun, 2 Sep 2018 at 20:40, Ian Foote wrote:
> On 02/09/18 19:59, Shivam J
On 02/09/18 19:59, Shivam Jindal wrote:
> Hi Lan,
>
> *m.user.refresh_from_db()* is sam as
>
> *u = m.user*
> *u.refresh_from_db()*
>
> So If I am refreshing u, it should update all relationship and property
> of *u*(including reverse relation). Should It not?
>
Hi Shivam,
As far as I can te
Hi Lan,
*m.user.refresh_from_db()* is sam as
*u = m.user*
*u.refresh_from_db()*
So If I am refreshing u, it should update all relationship and property of
*u*(including reverse relation). Should It not?
On Mon, Sep 3, 2018 at 12:24 AM, Ian Foote wrote:
> On 02/09/18 17:58, Shivam Jindal wrote
On 02/09/18 17:58, Shivam Jindal wrote:
> I have the following model
>
> class Member(models.Model):
> user = models.OneToOneField(User, null=True, blank=True)
>
> *Operation sequence*
>
> m = Member.objects.get(id=4) # This objects has attached user
> m.user # Print user objects successfull
I have the following model
class Member(models.Model):
user = models.OneToOneField(User, null=True, blank=True)
*Operation sequence*
m = Member.objects.get(id=4) # This objects has attached user
m.user # Print user objects successfully
m1 = Member.objects.get(id=4) # Fetch same object from d
