bugGNU Parallel - Bugs: bug #43191, Idea: output --result-sql in...

 
 

bug #43191: Idea: output --result-sql in sqllitebase

Submitter:  Ole Tange <tange>
Submitted:  Thu 11 Sep 2014 06:36:46 AM UTC
   
 
Category:  None Severity:  1 - Wish
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  tange
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 03 Jan 2016 11:48:24 PM UTC, comment #1: 

Fixed in [f4c20c13].
Except for bug #46803.

Ole Tange <tange>
Group administrator
Thu 11 Sep 2014 06:36:46 AM UTC, original submission:  

Instead of using R/Python Pandas to read the dir structure why not put the output directly in an SQLite base?

Columnns like: V1 V2 STDOUT STDERR <columns from --joblog>

Or if the columns are named: foo bar STDOUT STDERR <columns from --joblog>

How easy is it to insert rows like that? How big can they be?

It should probably be done from GNU Parallel itself. How do we avoid depending on SQLite.pm (Maybe eval "use SQLite"?)

Or could the output simply be generic SQL insert statements that would work on other SQL systems, too?

In that case how should --resume(-failed) work?

Ole Tange <tange>
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 tange (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.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-01-03 tange StatusNone Fixed
        Assigned toNone tange
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code