Sorry ,
I assume this is out of date meanwhile.
- Log in to post comments
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry Chip,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry Peter,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry ,
I assume this is out of date meanwhile.
Sorry Matt,
I assume this is out of date meanwhile.
Sorry Rich,
I assume this is out of date meanwhile.
Sorry Jean,
I assume this is out of date meanwhile.
Sorry Michael,
I assume this is out of date meanwhile.
sorry Chip,
I assume this is out of date meanwhile.
sorry Rich. this seems to be outdated.
all examples in OEX refer to Oauth 2.0
and that's the effective code behind
just checked:.png)
A typical use case is WebTerminal !
YEAH! A history track makes it definitely more complex
Thanks for the hint.
The review is imported from @Yuri Marx but the import flag * got lost , fixed
.
Why together ? ? ? Who wants that ? ? ? Where ? ? ?
A simple MERGE ^archive(....)=^source(....) just doesn't maintain any index.
this was my message
You have a lucky design without indices. That makes life with 2 distinct globals easy.
The archiving action maintaining the original ID could be achieved by a simple
MERGE from ^source to ^archive. maintenance of indices could be slightly
effort requiring class methods.