Something like this?
while (ind '= ""){
set row = ^CacheTemp(repid,"MAIN",ind)
if row [ "keyword" {
use filemain write row,!
} else {
use filemain2 write row,!
}
; Get next row index for MAIN report
set ind = $order(^CacheTemp(repid,"MAIN",ind))
}
close filemainCan you show your code and explain what are you trying to achieve?
set n=10
for i=1:1:n { write "set txt("_i_")="""_i_"""",!}Would output
set txt(1)="1"
set txt(2)="2"
set txt(3)="3"
set txt(4)="4"
set txt(5)="5"
set txt(6)="6"
set txt(7)="7"
set txt(8)="8"
set txt(9)="9"
set txt(10)="10"
You can paste it where needed.
Sure, why not?
There are already prebuilt docker containers, just pull it from docker hub:
docker pull intersystemscommunity/irispy:latest
The binaries are available from the releases page.
I completely agree, and to get to
standard installing mechanism
for USERS, we need to zpm-enable as many existing projects as possible. To enable these projects we need to simplify the zpm-enabling, leveraging existing code if possible (or not preventing developers from leveraging the existing code). I think allowing developers to use already existing installers (whatever form they may take) would help with this goal.
Great article!
I have some questions:
I completely support inclusion of projections.
ObjectScript Language allows execution of arbitrary code at compile time through three different mechanisms:
All these instruments are entirely unlimited in their scope, so I don't see why we need to prohibit one way of executing code at compilation.
Furthermore ZPM itself uses Projections to install itself so closing this avenue to other projects seems strange.
Great to hear that!
If you're interested in performance, upgrading to 2016.2+ would help tremendously with JSON processing due to the addition of dynamic objects.
Furthermore, upgrading to IRIS 2019.1.1 would add %JSON.Adaptor which simplifies JSON (de)serialization of normal objects.
Here's how.
1. Create a hardlink to the original database in a new empty folder.
2. Add this new database.
3. Mount new database as readonly.
4. Map package from this new database.
This way you can access code for RW (in original namespace/database) and RO (in hardlink database).
Just tried this setup and it worked.
I have found a workaround.
1. Create task class as usual.
2. Create this subclass extending (1)
/// Run it daily but it would actually run only on Dates
Class util.CustomDatesTask Extends util.BaseTask
{
Parameter TaskName = "BaseTask (random dates)";
/// Comma separated Dates in YYYY-MM-DD format
/// Example: 2019-12-11,2020-01-17,2020-02-11,2020-03-10,2020-04-09,2020-05-12
Property Dates As %VarString;
/// Check that Dates is valid
Method %OnValidateObject() As %Status
{
#dim sc As %Status = $$$OK
set sc = ##super()
quit:$$$ISERR(sc) sc
try {
set dates = $lfs(..Dates)
} catch ex {
set sc = ex.AsStatus()
set sc = $$$ADDSC($$$ERROR($$$GeneralError, "Incorrect Dates value: " _ ..Dates), sc)
}
quit:$$$ISERR(sc) sc
for i=1:1:$ll(dates) {
try {
set date = $lg(dates, i)
set temp = $zdh(date, 3)
} catch ex {
set sc = ex.AsStatus()
set sc = $$$ADDSC($$$ERROR($$$GeneralError, "Incorrect Date value: " _ date), sc)
}
quit:$$$ISERR(sc)
}
quit sc
}
Method OnTask() As %Status
{
#dim sc As %Status = $$$OK
set dates = $lfs(..Dates)
set curDate = $zd($h, 3)
if $lf(dates, curDate) {
// Execute the task
set sc = ##super()
}
quit sc
}
}The advantage is that schedule is easy to set as a task config property. Drawback is that logs would be created for each day.
Check this series of articles by @Daniel Kutac.
For example:
set maxrows = 1000
set currentrow = 0
while (ind '= ""){
set row = ^CacheTemp(repid,"MAIN",ind)
if currentrow>maxrows {
set currentrow = 0
// swap files
}
set currentrow = currentrow + 1
use filemain write row,!
; Get next row index for MAIN report
set ind = $order(^CacheTemp(repid,"MAIN",ind))
}
close filemainAre you by chance exporting SQL queries to CSV? If so it can be done automatically:
do ##class(%SQL.Statement).%ExecDirect(,"select * from ...")).%DisplayFormatted(100, filename)You need to specify pFormat parameter, it defaults to aceloqtw, where:
In your case explicitly remove c: aeloqtw. This is quoted from documentation.
Additionally if you want to output json to the current device it would be better to use %WriteJSONFromObject - it has the same arguments, except stream, so there's no extra object and io redirect costs:
$$$TOE(tSC, ##class(%ZEN.Auxiliary.jsonProvider).%WriteJSONFromObject(,Store,,,,"aeloqtw")Depends on a coding style.
I prefer not to use/propagate exceptions, but rather %Status.
Check Fileserver project for a demo of uploading and downloading streams/files.
It's a custom psudo-random day each month.
How to reschedule task on completion on a custom date?
For a second one, check documentation, "Nonexistent Table" section.
Thanks, Marc.
Found useful index:
write ##class(Ens.Config.Item).NameExists(##class(Ens.Director).GetActiveProductionName(),"HostName")
You need to index columns used in conditions, for the specified query:
If there are less than 6400 possible values you can use bitmap indices.
Start with individual indices (so the number of indices equals the number of condition columns).
Can/will moving to an async style of API help this?
No.
long strings aren't enabled in our instance(s) of Cache
You should enable long strings. That's been the default for years.
Anyway, use streams for response processing, they ignore string limits altogether.
It's not like that in the article.
Check Web Gateway timeouts, specifically Server Response Timeout setting. Also Web Server can impose additional limitations.
That said, I'd advice you to move to async style of API, here's how.
Currently you have one call, say /GetData and it takes 10 minutes.
Split it into 2 calls:
Here's a sample ASYNC REST broker.
This will save you a lot of problems down the line.
Shouldn't it be
zpm "install module-name"in dockerfile?
RabbitMQ adapter can work with Cache (in non-interoperability environments).
You can change the $HOME for cacheusr to some other dir, /home/cacheusr probably.
Well, as a cacheusr you don't have access to /root. Why not write into some temp directory?