Just a quick note.

I found that when creating a new database it was best to initially use SYS.Database so you can specifiy max size etc..

db=##class(SYS.Database).%New()
db.Directory=directory
db.Size=initialSize
db.MaxSize=maxSize
db.GlobalJournalState=3
Status=db.%Save()

Then finalise with Config.Database

Properties("Directory")=directory
Status=##Class(Config.Databases).Create(name,.Properties)
Obj=##Class(Config.Databases).Open(name)
Obj.MountRequired=1
Status=Obj.%Save()

This might not be the best way to do it, I'm open to improvements.

Hello Dmitry,

I have used the extension and am very impressed but obviously any change in toolset has to be agreed accross the business and will require changes to the development and version control process, hence a reluctance until we know what Intersystems have planned.

Apologies if I have missed a feature post but does the extension replicate the Studio Add-Ins such as the SOAP Wizard as these are very useful to us.

Regards

David

Hello Evgeny,

Thanks for the response, of course I am aware of the various plugins hence my question of relying on 3rd party tools.

That old post does not really answer the question on what Intersystems future plans for development tools are, it just confirms effective end of life for the current ones.   Also, only fixing critical issues means reported problems will generally not be fixed anymore as they are pretty stable, something I have already experienced.

I don't have a particular problem with moving to VSCode supported by 3rd parties but some confirmation of this from Intersystems so developers can plan to move in that direction would be appreciated but noone seeems to want to commit to any answers.  It also starts the question of how will Intersystems provide the ability for these 3rd party tools to replicate and extend the functionality available already, again there are no answers.

Regards

David

Hello Evgeny,

Slightly off-topic but it is interesting you are using VSCode.

I have asked at various times, including the last symposium, what the plans are for development tools given that both Studio and Atelier have essentially been end of life for quite a while now, well over a year, but the response is always the same, there is a plan but we cannot announce it yet. 

Is VSCode the way Intersystems is going?  Does this mean we are now relient on 3rd party development tools?  Are there plans to create some way to replicate functionality such as the SOAP wizard in VSCode?

I was hoping there might be some details out of the summit but I haven't seen anything yet.

Regards

David

A valid point but it can depend on how the command string is formed in the first place, unless you write a parser to break a command string down into a command plus arguements.  I agree that you may as well use $zf(-1 but as the documentation will point you to use $zf(-100 then it can be valid.

It's also usefull to know you can use brackets in this way for general knowledge.

This is a good idea, hopefully everyone will do this but I did have a problem.

Perhaps I have done this incorrectly but I could not see a way to submit screenshots in the challenge and when you click the "lets review" button,  or whatever the actual text was,  it closes it as completed and there seems no way to submit a screenshot.  Also, the link to the challenge is for the same challenge number as it appears in and it takes you to the Global Masters front page.

Also, you don't seem able to review both as suggested, if you use the link again or search for the platform you haven't reviewed yet it will simply state you have already submitted a review.  I suspect this is because using the link you have to choose between Iris or Cache and so the offer is for one or the other but not both.

If you have an equivalent version of Cache installed with the manager source code available then take a look at briefsub^%GSIZE. 

You can copy this code and amend as you require, remember to include the sub routines it calls and you will have to set a few things up first.  I've done similar things in the past on older systems, the code can look daunting at first but isn't hard to understand enough to use.

On newer systems you would use the %Library.GlobalEdit class.

Another clarification, ppg's are not limited only by disk space, just like all other databases the maximum size of cachetemp can be set to stop infinite growth, this means the ppg's have the same limit.

Also remember, the more you use them the more cachetemp fills.

One last point is that other parts of cache such as odbc queries also use cachetemp for storage and so the whole of cachetemp is not always available.

As ever you have to plan usage appropriately based on the application and the database configuration.