Ayon database write interaction

[Yul]

It was a Discord talk, then I realized it would be useful to save it for future search, so here is a copy :

@Yul

Hi,
I would like to know in which cases the Ayon’s database is written.

• A : When we publish. (in that case it’s obvious the database is written, as the WebApp “Browser” tab gets new informations).
• B : When we use the Workfile gui in a DCC. (probably, as the WebApp’s “Workfiles” tab has a list of them)
• C : When we create a new instance on a DCC (click on Create) ?
• D : When we use the Load gui in a DCC to load some products ?
• E : When we use the Manage gui in a DCC to change the version of some products ?

.

@Roy

• A → Yes, usually on integrate
  … … … Potentially also on ‘scene increments’ with future workfiles API, since that’d essentially trigger B.
• B → Yes, workfile entity info.
• C → No.
• D → No.
• E → No.

.

@Juan

I would add that [DB write also happens] whenever some Sync process is going on, like Ftrack/Shotgrid/Kitsu syncing back to Ayon, Ftrack is done via events, so if you have plugins/actions that may trigger certain events, there may be DB updates

.

@Yul

Thanks Roy and Juan

So, it means this :

• Good news : even if artists manually destroy stuff in DCC workfiles, for example loaded products, we can still load them again without getting double entry in DB.

• Bad news : there is no centralized database data that can answer this question : in which workfiles did we Load the product Starship v014 ?

.

@Roy

Well, if you have published from that scene… then for maya, fusion and Houdini we collect input versions at the time of publishing. Not sure if we also collect all that are in the Workfile actually, I vaguely recall we did already but if not, would be trivial to add across all DCCs…

As such, publishes should have stored links to loaded versions.

The bad news there is that currently there isn’t any out of the box UI that will really display it for you

.

A feature request was created here :
https://feedback.ayon.app/p/allow-to-find-in-which-workfiles-some-products-have-been