I'd like to get an Intersystems expert reference to Eduard's method.
Would you encourage us to use such methods (like using $piece etc. to get info from inside objects)
Thanks,
Uri
- Log in to post comments
I'd like to get an Intersystems expert reference to Eduard's method.
Would you encourage us to use such methods (like using $piece etc. to get info from inside objects)
Thanks,
Uri
Hi Konstantin,
Can we install this project on Cache 2016.2 or does it need 2017 ?
I tried to install offline (becuse my server cannot get through to GITHUB(443)) and the installation failed on several errors.
Maybe I need more specific instructions for offline install ?
Uri
If you really want to make use of the "answered" feature you should allow the author of the question to mark a specific comment as "the right answer".
In this case - there is only one answer with a "chain" of comments.
So - I have no way to mark the specific comment that really answers the question.
Think about it.
Uri
OK Intersystems confirms that as from 2015 they moved back from %SYS.GSET to %GSIZE, and the new %GSIZE dosen't function the same.
They also confirmed that they didn't bother to document the changed because they thought that nobdy is using it' since it was supposed to be an internal function.
OK thanks, I'll do that
Thanks John
I'm afraid that's not entirely correct.
%GSET existed until Cache 5. Then it was changed to %SYS.GSET.
I do see %GSET in our new 2016 installations, but it does Not function same as SYS.GSET.
For example - one could Do ^%GSET and Do ^%SYS.GSET, in the 2016 %GSET you can't do it, you must supply some parameters.
Thanks Eduard,
We have just discovered that the class in question isn't a "real" class.
It is "%CacheSQLStorage" (we call it "a mapped class") so it is obvious why Cache won't let us add indices at all.
If one needs an new index for such a class - one will have to build and manage it by himself.
So - thanks, we can now close this post.
Uri
Hi Eduard,
I did mention that the new index was NOT created after rebuild.
Maybe you missed it, or do you mean that "rebuild indices" from the management portal is not relyable and we should use ##class(Package.Class).%BuildIndices() instead ?
Uri
Thank you Eduard.
To answer your question (1) :
I posted my question for one of our developers who added such an index and found that the index wasn't created after rebuild.
So I thought the reason might be that an indexed property cannot be null valued, I didn't bother to ask what will be the use of such an index...
From your answer I understand that this is NOT the reason why the index was not created, so we'll have to look somewhere else...
Thanks,
Uri
Thanks Tomas.
Yes we need to know the name of the remote user.
We use it for many purposes in our applications.
As I mentioned before - we used Activex to get dNET.Username but since we are moving to HTML5 we cannot use it anymore.
Uri