You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the QuerySetJob should be used for caching purposes, I think its ok if get_or_create is not supported. Can you provide a use case which required get_or_create on QuerySetJob?
The use case is same as of get_or_create in general when we want to fetch the entry if exists, if not create and then fetch. With this, it will also cache it after creating the entry.
How yould you handle the "created" flag in this case? To be consistent, it should only be true for the first "get" call. Later cached "get" calls would need to return False for "created".
No description provided.
The text was updated successfully, but these errors were encountered: