Search

.. An index on reg.mnr and bar.invnum will accelerate this. Ok so this is definetely Centricity Business aka Flowcast and not GroupCast. Generally speaking your query looks

an index for that field.http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=EEDI_search_tablesFields indexed in the search table are listed in the dropdown box

As %String = "", index As %String) As %String { if $isobject(value) { quit value.GetAt(index) } quit "" } } and then, you can use it in this way

private email, unless of course you wish to address me only.See "Newbie's Corner Index" for an index of all NewBies' Posts Hi, Mike! What about the option of passing an unlimited set

:^Package.ClassNameI for index^Package.ClassNameD for values^Package.ClassNameS for streamsCheck the class's Storage XML discover it's global structure. And what this bill says

mechanism including indexes. Even in key-value stores you cannot see or understand the sorting of indexes, you cannot easily reference data values in permanent storage

the methods DisplayToLogical/LogicalToDisplay and/or LogicalToStorage/StorageToLogical. Use %MVR For example:Class dc.test Extends %Persistent { Index ibar On bar; Property bar

it later as: set @gn@("index")="value" But! I'm having syntax at set gn=$name(..#GlobalName) What am I doing wrong? The syntax issue with your line `set gn=$name

].index('-')]): docSer1 = str(roman.fromRoman(params[i][:params[i].index('-')])) secPart1 = '-' for elem in params[i][params[i

slot in the storage definition. The "name" property on that slot will give you the storage index. You could then iterate through the global where the data is stored and do something

In the Inbound SQL Adapter settings, is it possible to specify more than 1 field as the Key Field Name? Because of the way the Query is being index in Ensemble by the Key Field

mart", where it is indexed and aggregated in various ways before being made available for analysis. Even so, the data marts in question may be hundreds of gigabytes in size

, and I have good reasons for it. Which are? Can you compare the performance to index opening: s p=##class(digi.packet).IDKEYOpen("packet", 5237) Yes, I can try it but how do

(processId) You can get the pid without iteration.set nsp=$znspaceset pid=^$|nsp|lock("^DBLock(""Patient"",1119102928)","OWNER")do $system.Process.Terminate(pid)|nsp| is only required for access to a lock in a different namespace.

Use case: small in-house hospital systems that query patient demographics via SQL. The new PAS being implemented in the near future will only support query/response via HL7. SQL