What do you mean? How does it look in config file?
In the best case like this:
{
"storage-driver": "devicemapper",
"storage-opts": [
"dm.directlvm_device=/dev/xdf",
"dm.thinp_percent=95",
"dm.thinp_metapercent=1",
"dm.thinp_autoextend_threshold=80",
"dm.thinp_autoextend_percent=20",
"dm.directlvm_device_force=false"
]
}Docker documentation explains setting direct-lvm in detail.
There are system implementations too:
>write $$toRoman^%bi.SWr.FolderTest(124) CXXIV >write $$toRoman^%bi.SWr.FolderTest(1245) MCCXLV
If you're sure that all your keys are consecutive integers, then use $order to get the last element, which would also be a count of them:
write $order(a(""),-1)Please share the usecase.
I'd start with setting the credentials in connection configuration. Should be enough.
If you want to connect to external database, couldn't you just provide domain name and password and authenticate with that?
KILLdes is a record for kill of descendents journaled as part of a higher-level kill inside of transaction.
So it's a Kill command.
%DeepSee.Utils:%FormatDate offers this options
Format a date value (in $H format) according to the format in pFormat. The format string can contain:
Added mm as Time Format and rebuilt cube. Got 01 instead of JAN.
Removed mm. Turns out, all you need to do is to use locale defaults in Locale Settings
Not that Count approach is while easiest, can significantly slower the query down.
Extending the adapter so you have an "after all rows" callback has speed advantage and also you wouldn't need to rewrite your queries to add Count().
Follow these steps:
Table should be gone after that.
If you already deleted the class in Atelier (and synced that change with a server) the the table would be gone too.
Use Send method:
Set httprequest = ##class(%Net.HttpRequest).%New()
Set httprequest.Server = "www.intersystems.com"
Set sc = httprequest.Send("PATCH", location, test, reset)Do you wan to do something specific with the last row or do you just want a callback after all rows?
If it's the later, you can subclass SQL inbound adapter:
Class Project.Ens.Adapter.SQLInbound Extends EnsLib.SQL.InboundAdapter {
Method OnTask() As %Status
{
Set sc = ##super()
// all rows were just processed
// add your logic here
Quit sc
}
}Other approach is to UNION a dummy row to the end of your query, or add COUNT() property.
Pinging @Alexander Koblov
Isn't it more like anonymous functions?
Currently not possible. Check @Gilberto Junior solution - it seems the closest to what you want.
Here's a series of articles on how to work with GitLab.
Like this?
write $case(condition, 1:"hello " _"world", 2:"name",:"!")
Hello world is a multiline expression.
Post Teste method?
I'd go with if, but you can also resolve case expression beforehand:
set condition = .... several lines of logic... write $case(condition, ...)
And condition then can be separaten into several different lines.
I'm against method chaining in general and several functions on one line/step in particular.
Each line should contain one small operation.
Maybe
Property TS As List Of %TimeStamp;
?
UPD. Nevermind, got it.
You can use Security.Services class, it can modify services programmaticaly.
SoapAction method keyword maybe?
What risk?
There are two distinct cases - where we have users/passwords in place or we don't.
In the first case container should use these passwords (via Durable %SYS) and they shouldn't be be superseded by anything happening with a container change.
In the second case we have some empty application - no users, no data and so specifying random password only adds unnecessary steps down the line.
There is one case where we need to force our container user to create new password - when we are:
in this case yes (when all conditions are met), password should be scrambled, but this situation is wrong on itself (mainly in storing passwords inside the container), and should be resolved by other means.
On non-prod servers we don't need that - developer/ci server should be able to pull the image and work with it.
On prod Durable %SYS should be used with secret password and not changed with each new app version, but rather through a separate process (once a year, etc).
I'd try to rework this method to avoid object access to speed it up. GetStored method can help. Article about it.
This feels more like a DevOps process, where coding is more acceptable. Anyway, maybe you need to ask a separate question on configuration synchronization best practices?
1. Import task has these two qualifiers:
displayerror displaylog
They do not affect import.
2. No. If you check exported xml, you can see that exported tasks do not contain IDs, so, on import they could not overwrite existing tasks. Not sure about how correlate/next work on ID fields btw.
Exporting and importing what is currently present is the best way.
It's the easiest way. The best way would be to write and document a script (ObjectScript code) that transforms base instance into what they need. This way changes are documented and adding another server is easy.
1. Execute this to get a list of available flags and qualifiers:
Do $System.OBJ.ShowQualifiers() Do $System.OBJ.ShowFlags()
Qualifiers are preferable to use.
2. I'd rather go with programmatic access. Write code that's:
What system task did you modify?
Please post the code you use to generate xml.
Sure.
After that you'll be able to search InterSystems documentation in Chrome address bar by typing:
i keyword
and pressing Enter.
Do you want to pull all the rows each time?
If so, just clear “key Field Name” setting and BS would process all rows every time it's run.