Re: PSPP-BUG: Section 9.4.2 documentation clarity/meaning issue

[knassen]

Thanks, Ben!  I was able to import data from PostgreSQL the other day, so that was cool.

 

That paragraph looks a lot better now.

Kent

 

From: Ben Pfaff <blp@cs.stanford.edu>
Sent: Saturday, March 18, 2023 3:11 PM
To: knassen@chartermi.net
Cc: bug-gnu-pspp@gnu.org
Subject: Re: PSPP-BUG: Section 9.4.2 documentation clarity/meaning issue

 

Thanks for the report. I improved the paragraph for clarity and active/passive voice by editing it to:

 

   'GET DATA /TYPE=PSQL' imports data from a local or remote Postgres
database server.  It automatically creates variables based on the table
column names or the names specified in the SQL query.  PSPP cannot
support the full precision of some Postgres data types, so data of those
types will lose some precision when PSPP imports them.  PSPP does not
support all Postgres data types.  If PSPP cannot support a datum, 'GET
DATA' issues a warning and substitutes the system-missing value.

 

On Sun, Mar 12, 2023 at 12:05 PM <knassen@chartermi.net> wrote:

Here’s something in the PDF of the pspp manual that I couldn’t figure out reliably.  See Section 9.4.2 Postgres Database Queries.  The sentence fragment is “Postgres data types of high precision, loose precision when imported into PSPP.”  Perhaps that “when” needs to be fixed, e.g., “can/cannot be imported.”  Or maybe more needs to be added at the end of the sentence, e.g. “into PSPP become [something else].”  Or maybe the issue is around “loose precision, e.g., “converted to loose precision when imported.”  I’m not sure. 

 

In any event, I think that part of the documentation needs some editing to make the situation clear.

 

 

_______________________________________________
Bug-gnu-pspp mailing list
Bug-gnu-pspp@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-gnu-pspp