Wrapping bash command that is a string

Question

So I have this bash command:

sqlite3 ${SUMAN_DATABASE_PATH}  "CREATE TABLE suman_run_info (run_id INTEGER, suman_id INTEGER, suite_id INTEGER, test_id INTEGER,
 name TEXT, value TEXT);" >> ${SUMAN_DEBUG_LOG_PATH}

I want to wrap it manually in my editor. However since it's mostly a string, I can't seem to wrap it with the \ character.

A.k.a, this is not really going to work, tmk:

sqlite3 ${SUMAN_DATABASE_PATH}  "CREATE TABLE suman_run_info \ (run_id INTEGER, suman_id INTEGER, suite_id INTEGER, test_id INTEGER,
 name TEXT, value TEXT);" >> ${SUMAN_DEBUG_LOG_PATH}

How can I wrap this bash command so that it fits within 100 columns or whatever?

I am looking for something like this:

sqlite3 ${SUMAN_DATABASE_PATH}  "CREATE TABLE suman_run_info (run_id INTEGER, 
     suman_id INTEGER, suite_id INTEGER, test_id INTEGER,
     name TEXT, value TEXT);" >> ${SUMAN_DEBUG_LOG_PATH}

I have read that adjacent strings should auto-concat, so maybe this works?

   sqlite3 ${SUMAN_DATABASE_PATH}  "CREATE TABLE suman_run_info" 
   "(run_id INTEGER, suman_id INTEGER, suite_id INTEGER, test_id INTEGER,"
     "name TEXT, value TEXT);" >> ${SUMAN_DEBUG_LOG_PATH}

As an aside -- POSIX specifies all-caps names for variables with meaning to the OS or shell, and reserves names with lower-case characters for application use, guaranteeing that lower-case names won't conflict with reserved words meaningful to the OS or shell. See pubs.opengroup.org/onlinepubs/9699919799/basedefs/…, fourth paragraph, keeping in mind that setting a shell variable with a name that conflicts with an existing environment variable will overwrite the latter. — Charles Duffy
– Charles Duffy, Commented Jun 15, 2017 at 21:22
Re: "adjacent strings auto-concat" -- presumably that's in reference to 'foo'"bar"baz, but that's not actually two (or three) adjacent strings at all; it's one string composed with characters quoted in three different styles. — Charles Duffy
– Charles Duffy, Commented Jun 15, 2017 at 21:24

chepner · Accepted Answer · 2017-06-15 21:27:06Z

5

You don't need anything, in this case at least; SQL can handle newlines in the command without a problem. This should work just fine:

sqlite3 "${SUMAN_DATABASE_PATH}"  "CREATE TABLE suman_run_info
  (run_id INTEGER, 
   suman_id INTEGER,
   suite_id INTEGER,
   test_id INTEGER,
   name TEXT,
   value TEXT
  );" >> "${SUMAN_DEBUG_LOG_PATH}"

answered Jun 15, 2017 at 21:27

chepner

538k77 gold badges594 silver badges746 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

mauro · Accepted Answer · 2017-06-15 21:34:41Z

2

Be sure to have nothing after the backslash:

sqlite3 ${SUMAN_DATABASE_PATH}  "CREATE TABLE suman_run_info \
    (run_id INTEGER, suman_id INTEGER, suite_id INTEGER, \
    test_id INTEGER, name TEXT, value TEXT);" >> ${SUMAN_DEBUG_LOG_PATH}

Or, even better (see comments here below):

 sqlite3 "${SUMAN_DATABASE_PATH}"  "CREATE TABLE suman_run_info \
    (run_id INTEGER, suman_id INTEGER, suite_id INTEGER, \
    test_id INTEGER, name TEXT, value TEXT);" >> "${SUMAN_DEBUG_LOG_PATH}"

edited Jun 15, 2017 at 21:34

answered Jun 15, 2017 at 21:22

mauro

6,0262 gold badges31 silver badges27 bronze badges

1 Comment

Charles Duffy Over a year ago

Should quote the expansion of $SUMAN_DATABASE_PATH and $SUMAN_DEBUG_LOG_PATH -- otherwise they're vulnerable to splitting on characters in IFS (or, by default, whitespace).

Alexander Mills · Accepted Answer · 2017-06-15 22:37:35Z

1

I like to use HEREDOCs:

sqlite3 ${SUMAN_DATABASE_PATH} <<EOF  >> ${SUMAN_DEBUG_LOG_PATH}
CREATE TABLE suman_run_info
  (run_id INTEGER, 
   suman_id INTEGER,
   suite_id INTEGER,
   test_id INTEGER,
   name TEXT,
   value TEXT);
EOF

edited Jun 15, 2017 at 22:37

Alexander Mills

102k167 gold badges549 silver badges936 bronze badges

answered Jun 15, 2017 at 22:10

therealneil

5,4101 gold badge35 silver badges47 bronze badges

5 Comments

Alexander Mills Over a year ago

huh but would this work multiple times in the same file? I think not right? idk

therealneil Over a year ago

@AlexanderMills, without knowing your specific use-case, I would guess that a HEREDOC would work just as well as a string literal.

Alexander Mills Over a year ago

I thought you could only use one HEREDOC per file

therealneil Over a year ago

@AlexanderMills, my experience suggests otherwise.

Alexander Mills Over a year ago

huh, the semantics of EOF (end of file) ... I always assumed you could only have one

Collectives™ on Stack Overflow

Wrapping bash command that is a string

3 Answers 3

Comments

1 Comment

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related