bugPSPP - Bugs: bug #38682, Documentation for UPDATE is unclear

 
 

bug #38682: Documentation for UPDATE is unclear

Submitter:  John Darrington <jmd>
Submitted:  Mon 08 Apr 2013 07:35:03 AM UTC
   
 
Category:  Documentation Severity:  5 - Average
Status:  Fixed Assigned to:  None
Open/Closed:  Closed Release:  Before 0.8.0
Effort:  0.00
* Mandatory Fields

Add a New Comment Rich Markup
   

Fri 17 May 2013 04:51:01 PM UTC, comment #1: 

This was actually mentioned in the manual, but very briefly.  I expanded that a little to make it more obvious.

John Darrington <jmd>
Group administrator
Mon 08 Apr 2013 07:35:03 AM UTC, original submission:  

Ronald Crichton wrote:

   I now realise that the PSPP update command reads data from the Master file
     and reads data from the Transaction file and from this data the 'active'
     file is manipulated to reflect the intended updates.  The original data in
     Master remains unaffected.  At the end of the run nothing changes.  To
     retain the updates the active file must be saved.


     The user manual is a little ambiguous in this regard. The first sentence
     states "UPDATE updates a master file..." which is not quite correct, as the
     master file is not updated.   Then the first dot point refers to values
     being replaced "in the new active file."  I missed this on my first reading
     of the manual.  May I suggest the manual be changed to make it clear that
     the master file is not actually updated and that the active file must be
     saved to retain a permanent record of the updates

John Darrington <jmd>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jmd (Submitted the item)
  • -email is unavailable- added by jmd
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-05-17 jmd StatusNone Fixed
        Open/ClosedOpen Closed
    2013-05-11 jmd ReleaseNone Before 0.8.0
    2013-04-08 jmd Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code