Jump to content

session.get('TypedContext', entity_id) not working


Recommended Posts

Hi Mark,

TypedContext works for task, milestone and other Objects that you can dynamically add and remove from System settings (like Shot, Sequence and so on). For other entities such as Note or AssetVersion you will need to use session.get('AssetVersion', version_id) or session.get('Note', note_id) 

Link to post
Share on other sites
  • 6 months later...
On 9/29/2016 at 9:50 AM, Mattias Lagergren said:

For other entities such as Note or AssetVersion you will need to use session.get('AssetVersion', version_id) or session.get('Note', note_id) 

Works with session.get('Note', note_id), but if I have only the id, not also the entity type, how can I get the entity?

Link to post
Share on other sites
On 07/04/2017 at 7:42 AM, Remus Avram said:

Works with session.get('Note', note_id), but if I have only the id, not also the entity type, how can I get the entity?

You only have the id and no information at all about the type of entity? There is no real good solution for that I'm afraid. Testing/Guessing is of course possible, but for performance reasons I would recommend that you try to keep identity of the entity and the entity type together.

Link to post
Share on other sites

We are using session.get('TypedContext', entity['id']) in order to check if the entity still exists before committing changes.

If we keep the entity type and id, then we suppose to check if the entity still exists if we run: session.get(entity.entity_type, entity['id'])

Unfortunately, if the entity doesn't exists any longer, we get different results:

session.get(entity.entity_type, entity['id'])

Returns:
<dynamic ftrack Task object 139839326832592>

When:

session.get('TypedContext', entity['id'])

Returns:

None

In order to get it right, we must clean the cache all the time before:

self._session.cache.clear()

 

Link to post
Share on other sites

I got SYMBOL(NOT_SET) random when getting the custom attributes value without cleaning the cache.

But I think that one is another story.

session.get(entity.entity_type, entity['id'])

is getting the data from the cache, which from my point, for scripts which run for long time, doesn't make sens because the cache is not updated.

Link to post
Share on other sites

ok, I am having sessions that change their "auto_populate" value to "False" somehow... I cannot get my head around this, but setting it to "True" right before a get does do the trick.
I just fell because I was using task.get("parent") and the pointer on task was not using my global session object but a copy of it, hence I had to set ```task.session.auto_populate = True```

Link to post
Share on other sites
59 minutes ago, Nebukadhezer said:

ok, I am having sessions that change their "auto_populate" value to "False" somehow... I cannot get my head around this, but setting it to "True" right before a get does do the trick.

That sounds wrong, can you reproduce this behaviour some how? It would help us track down the bug if there is one.

Link to post
Share on other sites
21 hours ago, Remus Avram said:

ok, but then way this method query the DB and not using the cache?


session.get('TypedContext', entity['id'])

Great input and I haven't thought about this before. The reason is that the identity of the object you get is a Task|Shot|Sequence|Folder|etc. and that is how it is cached. When you do the get on TypedContext the backend will figure out the correct subclass entity and return that. When the server request is done it will be merged into whatever exists in the memory cache.

If you do this instead you will get it straight from the cache:

session.get(entity.entity_type, entity['id'])

Using get with TypedContext is good when you do not know the sub-class entity type.

Link to post
Share on other sites
  • 2 months later...
On 4/20/2017 at 7:21 PM, Mattias Lagergren said:

No, I think in that case you should go for session.query as that will always query the server. It does however still merge it with the local cache.

Unfortunately, session.query does not always query the server...  

Example: I create an assetBuild and a child task and in the same session, I query for the assetBuild and check for the children.

Randomly, both session.get and session.query returns len(ftrack_asset['children']) = 0. 

Only after clearing the cache it returns the right data.

(Pdb) len(ftrack_asset['children'])
0
(Pdb) ftrack_asset = self._session.get('TypedContext', ftrack_asset['id'])
(Pdb) len(ftrack_asset['children'])
0
(Pdb) ftrack_asset = self._session.query("{0} where id is '{1}'".format(ftrack_asset.entity_type, ftrack_asset['id'])).one()
(Pdb) len(ftrack_asset['children'])
0
(Pdb) self._session.cache.clear()
(Pdb) ftrack_asset = self._session.get('TypedContext', ftrack_asset['id'])
(Pdb) len(ftrack_asset['children'])
1

Is it possible to create an ftrack session without using the cache at all?

Link to post
Share on other sites
  • 1 month later...
On 4/8/2017 at 7:55 PM, Mattias Lagergren said:

You only have the id and no information at all about the type of entity? There is no real good solution for that I'm afraid. Testing/Guessing is of course possible, but for performance reasons I would recommend that you try to keep identity of the entity and the entity type together.

Keeping the id and the type of the entity together works for us pretty nice. 

But in the event hub, the event['data']['selection'] contains the id and the 'context_type' of the entity instead of the type of the entity. In this case we can't get nice the entity.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...