Zugg Software :: View topic

Novice Joined: 26 Jan 2009 Posts: 32

#DBLOAD Actions
#DBFIRST
#VIEW All
#DBFIRST
#LOOPVIEW {#SHOW &Num}
#LOOPVIEW {} {#SHOW &Num}
;Above Produces no output
#LOOPVIEW {All|Actions} {#SHOW &Num}
#LOOPVIEW {All|ac} {#SHOW &Num}
#LOOPVIEW "All|ac" {#SHOW &Num}
#LOOPVIEW All {#SHOW &Num}
#LOOPVIEW All|ac {#SHOW &Num}
#LOOPVIEW All|Actions {#SHOW &Num}
;All of the above produce a loop of #SENDS based on the Database View|dBName

#LOOPVIEW "#SHOW &Num"
;Works!?!

Posted: Mon Jan 26, 2009 6:08 pm

This is because the database module was directly ported from zMUD and requires a string argument to it's database commands and functions. This will be fixed whenever the database module is rewritten for CMUD, but that's going to be a while.

So, as you noticed, you need to put quotes around the entire command for #LOOPVIEW instead of using {} whenever you use the &Column syntax.

Novice Joined: 26 Jan 2009 Posts: 32

If the database module is a direct port then I suspect the %query function will produce database corruption when searching for Boolean values depending on the current view of the dB applet. I was forced to write my own ZMud query functions to avoid this corruption. If anyone can use this CMud code please do:

<func name="DBQUERY" id="894">
<value>#LOCAL $Result
#DBOFFLINE
#DBLOAD $Database
#DBFIRST
#VIEW $View
#DBFIRST
#QUERY {(%string($Query))} {} {1}
#DBFIRST
$Result = %rec
#DBONLINE
#RETURN $Result</value>
<arglist>$Database,$View,$Query</arglist>
</func>

The excessive use of DBFIRST is used to avoid 0's appearing in set column's of a database you happened to be viewing.

Please note this will only produce one result, which is fine for what I needed to do. You could add a #WHILE (not null (%rec) {#DBNEXT;#ADDITEM $Result %res;#DBNEXT;} to return all results. or use &Num instead of rec to get the numbers instead.