Is this beta still open?  I heard the date was extended.

Daniel, 

Excellent article both from a historical and current perspective!

Rich

I think there is a little confusion here.  That quoted description of look ups is how Multivalue works with its Hashed storage structure.  Cache does NOT use a hashed storage model.

The point I really wanted to make is that  Cache data files, which we refer to as Globals, do not require you to perform any kind of resizing the same way you did with Universe/Unidata.  Thus reducing your operational maintenance.  In addition the database as a whole, which contains all the 'globals', will grow dynamically as more data is loaded.    

If you want to PM me I could set aside some time to do a short teams call with you.

Regards,

Rich Taylor

Robert,

I'd be happy to respond.  First I want to confirm/clarify some things.  When you say that you have a Universe database "attached" to Cache I am assuming you mean that you have migrated said database to cache and the data is now stored natively in Cache.

So the short answer is that you never need to do resizing in Cache as was required in Multivalued databases like Universe and Unidata.  The reason for this is that the fundamental storage methodology is quite different.  

In Multivalue (MV) each table/file/Global (to use a Cache term) is a hashed entity.  When created it  starts with a known number of groups that comprise the storage for that table.  Every record stored is "hashed" to determine which group it belongs in.   Another part of defining a hashed table in what MV calls a separation.  This is an indication of the database block size.  As data is inserted into the table groups will tend to fill up.  At this time a new block is added to the group so that new records can be stored.  In a hashed table a give record key will only ever hash to the same existing group.  When looking up a record hashing to the group is very fast.  However once in the group the lookup is a linear function that examines every record in every block of the group to find the record being retrieved. Inserts are always appended to the end of the group.   This is what tends to slow down an MV system.  Pick a poor initial group size or separation size and performance will suffer.  This is the reason for the need to RESIZE.

Cache, at its base table storage level, behaves similar to a key-value store which is internally implemented as a high-performance binary structure.   No hashing is preformed and key look-ups and inserts are consistently extremely fast.  I would also like to correct one thing you stated.  You don't have to be concerned with the initial size of the Cache database as you indicated though getting size close to what is needed is always recommended.  The database can grow dynamically as records are added.  It will grow up to the maximum size of a Cache database within any OS level limitations.  The only performance concern would be disk level fragmentation.  

I hope this helps.  If you have any further questions please reach out. 

Regards,

Rich Taylor

David,

The issue you will face is that the browser features that Raj has mentioned are core to the ZEN framework.  These features have been deprecated for many years now but have not been removed due applications, such as ZEN, still relying on them.   However, there will come a time where the technical debt of maintaining long deprecated features will become too much.  Its not a matter of if, it is a question of when.   This may not happen for another 10 years or the announcement could come tomorrow.  This ambiquity would certainly make me nervous.  Once one major browser vendor remove these features the rest will quickly follow.

Further attempting to modernize ZEN to work with current web technology would be a quite sizable task and could never hope to reach feature parity with more broadly accepted frame works like Angular and the others listed above.

My advice would be to start looking at which framework best meets your needs (I'm an Angular fan) and begin an effort to convert your screens to that framework and convert any back-end code that needs accessed from the front-end to REST services.  Do this over time converting one module or even sub-module at a time.  Start with several smaller areas so you can gain knowledge and experience.  As you build out your REST services you will undoubtedly discover improvements that would require refactoring previous work.  The smaller modules will make this easier to swallow.

Adam,

First a disclaimer.  I have not worked with Polybase in MS SQL Server. 

From a purely ODBC access perspective my initial thought is the driver you are using is wrong.  Try using the InterSystems ODBC driver which you can obtain from the Software downloads area of the Worldwide Response Center web page.  (https://wrc.intersystems.com/wrc/coDistGen.csp)

Here is the docs for creating an IRIS ODBC datasource on windows just in case.  https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=BNETODBC_winodbc

Hope that helps

Regards,

Rich Taylor

You can try signing out of the account.  Then you would have to go through the sign-in process again.  Look for the Accounts icon in the lower left corner of VCS. 

Click it and find the namespace you are logging into in the list.  Click the arrow to the right of the name and sign out.

If you have a folder associated with a namespace that is still blocking you this folder should appear in the Explorer window on the left side of VCS.  Right click the top level of the folder and find the "Remove Folder from Workspace" option.  It should be in the middle of the menu.  That will remove it from your workspace and allow you to switch.

There are two projects in Open Exchange.  I have not worked with them myself, but you could use them as a starting point at least.

https://openexchange.intersystems.com/package/blockchain---%5B-IRIS--python-%5D

https://openexchange.intersystems.com/package/Ethereum-Interoperability-Adapter

Or use embedded Python

for x in [1,2,3,4,5,6,7,8]:
  print('this is x: '+repr(x))

I would look at the %Library.PosixTime (%PosixTime) class.  I have used this for similar functions in the past.

https://docs.intersystems.com/irisforhealthlatest/csp/documatic/%25CSP.D...

There are two thoughts I have on this example:

• The use of %All is a very bad idea.  This gives the maximum permissions to the connection.  Having just attended a seminar on penetration testing it is frightening how small gaps in security can be exploited to compromise a system.  Better to identify the specific resources  and roles needed for this action to complete and give only those.
• Authentication is only taking place after the connection has "breached the castle walls".   The code is already running inside you environment and with %All privileges

Your utility methods are fine.  However I would implement them using Delegated Authentication.  This feature of IRIS allows you to provide your own code to do authentication.  The difference is that it executes as part of the normal authentication process.  The connection has not yet gained access to the environment and will not gain access if authentication is not passed.  Any failure or attempted breach of the code causes an "Access Denied" message to be returned and the connection terminated.  It is also possible to use this in combination with other authentication methods so this only needs to be used on REST services where it is needed.  This would also remove the need to add any special permissions like %All to the Web Application definition.  Here is the documentation for this.

Delegated Authentication

This command will do this also:

set str ="$lb("""_$replace($listtostring(x),",",""",""")_")"

There is a caveat though,  If the list is empty the $listtostring() will through a NULL exception. So you will need to check for an empty string.

First I have had success just leaving the GetCredentials out, but you are correct in that the documentation says you should have this.  Change your GetCredentials code to be just

return $$$GetCredentialsFailed

This will cause the process to revert to normal username and password prompting.   You only need to implement GetCredentials code if you are pulling the username and password from somewhere else such as taking the authentication header out of a REST call.

Link to the docs   https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GAUTHN_delegated#GAUTHN_delegated_zauthgetcreds