 |
atpeace
Novice
Joined: 26 Jan 2009
Posts: 32
|
 Posted: Mon Jan 26, 2009 2:45 pm
#DBDELETE Does not nothing in #DBOFFLINE Mode
|
As in ZMud #DBDELETE Does nothing if the Database is set to offline
#DBOFFLINE
#DBLOAD Actions
#DBFIRST
#VIEW All
#DBFIRST
#WHILE (not %null(%rec)) {
#ECHO &Num
#DBDELETE &Num
#DBNEXT
}
#DBONLINE
;Produces a list of correct database numbers but does not delete them |
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Mon Jan 26, 2009 3:52 pm
|
This is the correct functionality of #DBOFFLINE.
Per #HELP #DBOFFLINE (entered into the command line)
| Quote: |
| "Puts the database into Offline mode so that scripting commands do not effect the user interface." |
Basically means you can't edit it while it's in Offline mode, something I enjoy very much.
Charneus |
|
|
|
|
atpeace
Novice
Joined: 26 Jan 2009
Posts: 32
|
Posted: Mon Jan 26, 2009 4:05 pm
|
Well I'm sorry to say but all my database editing is done in offline mode else you get a significant performance hit
You can #DBPUT, #DBGET, #VIEW, #DBLOAD, #DBNEXT, use &(dbvar) for retrieval and assignment, %rec and more in #DBOFFLINE mode. The only thing you can't do is DBDELETE.
The offline mode surely is so you can script actions on the database without it updating the view (as all my functions do) else you would have to accept the performace hit of the view updating.
What exactly is the point of offline mode if it is not for scripting? |
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Mon Jan 26, 2009 4:09 pm
|
*shrug* Maybe I misinterpreted the vagueness of the helpfile, then.
In any case, I've never suffered a 'significant performance hit' because all my db editing is done online. In fact, I just deleted over 1200 records without a hint of lag. *shrug*
Charneus |
|
|
|
|
|
|
|
