Installation Manifest - I can disabled the journal globals by the XML?

Question

Question

Lucas Scarduelli · Jun 21, 2018

#Continuous Integration #Databases #System Administration #Caché

I'm creating a new namespace by the installation manifest XML and in the "database" tag configuration I don't see attribute to configure if I what jounal globals or not to this database.

In the database wizard of the "portal administration", have this option.

Regards,

Lucas Boeing Scarduelli

Discussion (8)2

Log in or sign up to continue

Eduard Lebedyuk · Jun 21, 2018

You can call code from %Installer via Invoke tag (more on that).

To change journaling programmatically execute:

/// Change database journaling state.
/// dbDir - database Directory (can be passed relative to the current working dir)
/// journal - 1 or 0. 1 enables journaling, 0 disables it.
/// zw ##class(util.Test).JournalDB("USER", 1)
ClassMethod JournalDB(dbDir As %String, journal As %Boolean = {$$$YES}) As %Status
{
    quit:((journal<0) || (journal>3)) $$$ERROR($$$GeneralError, "Invalid journal value. 0 or 2 for No, 1 or 3 for Yes")
    set:journal=$$$YES journal=3
    set:journal=$$$NO journal=2

    new $namespace
    set $namespace = "%SYS"
    set db=##Class(SYS.Database).%OpenId(dbDir)
    set db.GlobalJournalState = journal
    quit db.%Save()
}

That said, any particular reason you want unjournaled databases?

2 0

score 0 · Answer 1 · 2018-06-21T09:30:38-04:00

Hi, thanks!

We think of doing this way, but it would be more elegant if we had an attribute in the tag <Database>.

This database is created dynamically to CI, so we want unjournaled databases, to not to take up too much disk space.

score 1 · Answer 2 · 2018-06-28T13:39:47-04:00

Thank you for helping Eduard Lebedyuk.
Lucas Scarduelli and I followed that idea. Just by contributing, we developed the following method:

ClassMethod disableJournaling(databaseDir As %String = "")
{
   #dim database As SYS.Database = ""
   #dim error As %RegisteredObject = ""
   #dim currentNamespace As %String = $namespace

   try {
       znspace "%SYS"

       set database = ##class(SYS.Database).%OpenId(databaseDir)
       do database.DisableJournaling()
       $$$ThrowOnError(database.%Save())

       znspace currentNamespace
   } catch error {
       znspace currentNamespace
       do error.Log()
   }
}

score 1 · Answer 3 · 2018-06-21T09:35:32-04:00

Eduard Lebedyuk · Jun 21, 2018

There is no such attribute in <Database> tag, unfortunately.

1 0

score 0 · Answer 4 · 2018-06-28T14:21:58-04:00

Are there advantages to using:

set currentNamespace = $namespace
znspace "%SYS"
// do stuff
znspace currentNamespace

Instead of:

new $namespace
set $namespace = "%SYS"
// do stuff

score 0 · Answer 5 · 2018-06-29T06:24:10-04:00

Probably not. But prior to 2010.1 we didn't have $NAMESPACE, and its forerunner $ZNSPACE couldn't be NEWed. So code might look like this:

set currentNamespace = $znspace
znspace "%SYS"
// do stuff
znspace currentNamespace

score 1 · Answer 6 · 2018-06-29T09:00:45-04:00

Cool, I learned using ZNSPACE (in the 2008 version) to change between namespaces in the routines. Looking at the documentation actually recommends the 'set $namespace = ... '. Caché always surprising ...

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_cznspace

score 1 · Answer 7 · 2018-06-29T11:52:23-04:00

But prior to 2010.1 we didn't have $NAMESPACE

As @Lucas.Fernandes uses $namespace in his solution:

 #dim currentNamespace As %String = $namespace

that is not a concern in this particular case.