Tortoise-orm: Should a nullable ForeignKeyField return null even though it exists but just hasn't been fetched/prefetched?

[mojimi]

Should a model instance nullable ForeignKeyField return null when it has not been fetched/prefetched? It feels counter intuitive to me, take the following example

class Task(BaseModel, TimestampMixin):
    mother_task = fields.ForeignKeyField('models.Task', null=True)

    def has_mother(self):
        if self.mother:
            return True
        return False
...
task1 = Task()
await task1.save()
task2 = Task(mother_task=task1)
await task2.save()
...
if task2.has_mother():
    #This never prints
    print('Task 2 has a mother')

If I set it to nullable, and it return null, then I expect that it doesn't exist.

In the end I had to resort to the following :

...
async def has_mother(self):
    if self.mother_id:
        return True
    return False

Is this the intended way to go by?

[grigi]

Ah, I get it.

Even though the self.mother is a lazy awaitable, (e.g. you do an if await self.mother it would work), it knows it's not null. So I should implement a __bool__ operator?

Then this will be slightly less confusing.

Thanks for bringing this to my attention :smile:

[grigi]

I release v0.15.8 with a fix for this, please test :smile:

[mojimi]

Thank you it works