go to post John Murray · Nov 8, 2016 Does your where clause need a colon in front of pVariable ?where COLUMNC = :pVariableIf that doesn't fix it, I suggest you first check whether the problem is caused by the &sql(...) or by the way your web page is calling your server-side method.Remove all your code between the opening &sql( and the closing ) - incidentally, I assume you have a closing ) even though it didn't show in your post.Make your method end with QUIT pVariable instead of returning tempVariable1.Do you still get a Javascript error?
go to post John Murray · Nov 8, 2016 This is interesting, and highlights that the use of TSTART and TCOMMIT alone is not sufficient to give your transactions ACID properties.
go to post John Murray · Nov 8, 2016 Thanks moderator. Maybe the auto-split will do a better job someday.
go to post John Murray · Nov 8, 2016 When a MAC routine is compiled it generates and compiles an INT routine. When an INT routine is compiled it generates an OBJ routine.Here's one way to get the $H-style timestamp of when an OBJ was last written. In my example it's the OBJ of the RightTriangle.MAC example in the SAMPLES namespace:write $$DATE^%R("RightTriangle.OBJ")
go to post John Murray · Oct 27, 2016 For a class definition you can get the timestamp of last change from the TimeChanged property of the %Dictionary.ClassDefinition instance for the class.For a routine, the TimeStamp property of its %Library.Routine instance is what you want.But AFAIK the associated username isn't recorded automatically. You could use the server-side source control class interface to record this kind of thing, but it relies on whatever is making the change actually collaborating with that interface.Do you use any form of source control?
go to post John Murray · Oct 27, 2016 That'd rely on 2016.2.0 being able to restore the journals written by 5.0.21, right? I'm not saying that's not possible, just that it'd need to work correctly (i.e. not just appear to work).
go to post John Murray · Oct 18, 2016 I've just re-checked in the latest published build, 1.0.255. There's no sign of any improvement on these. I hope you haven't lost sight of them.
go to post John Murray · Oct 18, 2016 Any news on 2 and 3 yet? No sign of them in the latest build, 1.0.255.
go to post John Murray · Oct 11, 2016 Note that Atelier requires 2016.2 as the minimum version of the Cache/Ensemble instances you're wanting to connect to.
go to post John Murray · Oct 11, 2016 Great article Dmitry. I think there's a minor typo under the dump of the big string block. You wrote:Unfortunately, this block is shown unencrypted. I think you mean "encrypted". Or perhaps better to say "encoded", and to refer to "decoding" in the subsequent sentence instead of "decryption".
go to post John Murray · Oct 10, 2016 I cannot help with this, and I don't think Developer Community (DC) is the right place. You should contact WRC. See http://www.intersystems.com/services-support/worldwide-response-center/Please note that, like many participants on DC, I do not work for InterSystems.
go to post John Murray · Oct 10, 2016 I can't reproduce what you report.Please confirm that in the "Debugging Target" dialog the upper radiobutton is set and the adjacent input field contains this:##class( %SourceControl.UnitTest).Test()And if you comment out the "D $ZF(..." line in the classmethod, then recompile it, does that resolve the problem. If not, then I think this proves that the problem isn't caused by the $ZF() call.Also to say that if you need a response urgently you should contact InterSystems Support, a.k.a. WRC. This forum (Developer Community) is not a substitute for WRC.
go to post John Murray · Oct 7, 2016 You wrote:from Cache Studio, when I examine the output of the class given above, I get the error message:...Please tell us exactly how you are using the class from within Studio.
go to post John Murray · Oct 4, 2016 By adding that repo I was able to upgrade to 1.0.255.I guess that my original Atelier kit was built on Eclipse Mars, and that the developers recently moved up to Eclipse Neon but the upgrade mechanism didn't cope with this. Okay for a pre-release version of Atelier, but let's hope a similar thing doesn't happen once it's become a released and widely deployed tool.
go to post John Murray · Oct 3, 2016 This is with a standalone install of Atelier.I also have an Eclipse Mars.2 instance (Eclipse 4.5.2) that I had previously added Atelier 1.0.165 to. This one was able to upgrade Atelier to 1.0.255 successfully via "Check for updates".
