bugPSPP - Bugs: bug #48829, show all include postgresql...

 
 

bug #48829: show all include postgresql availability

Submitter:  Harry Thijssen <unknown_one>
Submitted:  Fri 19 Aug 2016 04:54:38 PM UTC
   
 
Category:  Compilation/Portability Severity:  1 - Wishlist
Status:  None Assigned to:  None
Open/Closed:  Open Release:  None
Effort:  0.00
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 31 Jul 2018 05:30:46 PM UTC, comment #8: 

A bit late :-)

> Mon 22 Aug 2016 04:53:30 AM UTC, comment #4:
>We already have a message like Ben suggests.


Is there indeed a message when PSQL is included? Or is there a way how I can see if PSQL is included in the binary?


Harry Thijssen <unknown_one>
Thu 25 Aug 2016 05:19:22 AM UTC, comment #7: 

I agree that a command line option such as --config would be more in line with the Gnu way of doing things.  On the other hand spss, which we claim to emulate,  apparently puts this information under SHOW ALL.

There is no reason why we couldn't do both.

John Darrington <jmd>
Group administrator
Mon 22 Aug 2016 05:10:26 PM UTC, comment #6: 

I think it is usefull for bug hunting. If a user has a problem and can generate as much info as possible as easy as possible and send it.

If I see how this is handled in SPSS I guess show all is the most likely place.


Harry Thijssen <unknown_one>
Mon 22 Aug 2016 03:43:58 PM UTC, comment #5: 


> It's true that some of the implementation detail would be exposed. Is that necessarily bad? My concern is doing it in a way which would continue to be maintainable.


I guess it wouldn't hurt anything, although a lot of users probably wouldn't understand what it meant.

Is this more useful as a runtime command or as something to show in, say, --version output?  What's the proposed use case for the information, in other words?

Ben Pfaff <blp>
Group administrator
Mon 22 Aug 2016 04:53:30 AM UTC, comment #4: 

We already have a message like Ben suggests.  However what Harry wants (I think) is a summary of optional features enabled (or not) when the software was built.

It's true that some of the implementation detail would be  exposed.  Is that necessarily bad?   My concern is doing it in a way which would continue to be maintainable.

John Darrington <jmd>
Group administrator
Mon 22 Aug 2016 01:18:02 AM UTC, comment #3: 

The COMPILE-OPTIONS that you suggest exposes a lot of implementation detail, I think.

It's not too hard to add a line like: "PostgreSQL is (not) supported," I guess.

Ben Pfaff <blp>
Group administrator
Sun 21 Aug 2016 09:15:34 AM UTC, comment #2: 


I think grouping the output could be usefull. For example phpinfo gives nices and usefull info I think. Also in spss the current show info does some grouping of the info.

I would prefer a table with the compile time options.


Harry Thijssen <unknown_one>
Sat 20 Aug 2016 07:21:33 PM UTC, comment #1: 

I'm thinking about how this could best be done.
I'm a bit worried about a possible proliferation of entries in SHOW ALL.
How would it be if we had a single entry containing a concatenated string of all compile time options? 

For example

COMPILE-OPTIONS = "PSQL_SUPPORT=yes GNM_READER_SUPPORT=no ODF_FEATURES=partial" .... etc

???

John Darrington <jmd>
Group administrator
Fri 19 Aug 2016 04:54:38 PM UTC, original submission:  

is it possible to include a message in show all if pspp was compiled with postgresql support?


Harry Thijssen <unknown_one>

 

(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 blp (Posted a comment)
  • -email is unavailable- added by jmd (Posted a comment)
  • -email is unavailable- added by unknown_one (Submitted the item)
  •  

    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.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-08-22 jmd Severity5 - Average 1 - Wishlist

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code