Ruby Multi-Line Strings Without Concatenation

By the end of this page, you will understand how Ruby handles multi-line strings and how to write long text more cleanly without using repeated + concatenation. You will see practical options such as heredocs, backslash line continuation, and adjacent string literals, with a focus on readable SQL queries.

Ruby gives you several ways to represent long strings across multiple lines. This matters because long strings appear often in real programs: SQL queries, HTML templates, error messages, JSON payloads, and command-line output.

The core idea is that you do not always need to build a long string with +. In many cases, Ruby lets you write text in a more readable form.

The most useful approaches are:

• Heredoc: best for long multi-line text such as SQL or templates
• Adjacent string literals: Ruby can combine neighboring string literals automatically in some contexts
• Backslash line continuation: keeps the string logically on one line in Ruby code

For SQL specifically, heredoc is usually the clearest choice because it preserves formatting and makes the query easier to read and maintain.

A key thing to remember is that multi-line source code and multi-line string content are not always the same:

• Sometimes you want the Ruby code on multiple lines, but the final string should be one line
• Sometimes you want the final string itself to contain line breaks

Choosing the right approach depends on which of those you want.

Think of a string like a note you want to write on paper.

• Using + is like cutting the note into pieces and taping them together.
• Using a heredoc is like writing the whole note naturally in one block.
• Using adjacent literals is like putting several note fragments next to each other and letting Ruby combine them.

If the content is naturally long, like an SQL query, heredoc is usually the most natural way to write it.

1. Heredoc

A heredoc lets you write a string block over multiple lines.

sql = <<~SQL
  SELECT attr1, attr2, attr3, attr4, attr5, attr6, attr7
  FROM table1, table2, table3
  WHERE table1.id = table2.table1_id
SQL

conn.exec(sql)

Why this is useful

• Very readable
• Great for SQL, HTML, JSON, and long messages
• Keeps the formatting close to how the final text should look

<<~SQL also removes common indentation, so your code can stay neatly indented.

2. Adjacent string literals

Ruby can join string literals written next to each other.

sql = 'SELECT attr1, attr2, attr3 ' 
      'FROM table1, table2, table3 ' 
      'WHERE table1.id = table2.table1_id'

conn.exec(sql)

This is much cleaner than using + repeatedly.

3. Backslash line continuation

If you want one logical string split across lines in code, you can continue the expression with \.

sql = 'SELECT attr1, attr2, attr3 ' \
      'FROM table1, table2, table3 ' \
      'WHERE table1.id = table2.table1_id'

This still relies on separate string literals, but the line continuation makes the code valid across lines.

Consider this example:

sql = 'SELECT name, email ' 
      'FROM users ' 
      'WHERE active = true'

puts sql

Step by step

1. Ruby reads the first string literal:

   'SELECT name, email '
   

2. Ruby sees another string literal immediately after it:

   'FROM users '
   

3. Ruby combines them into one string.

4. Ruby reads the third string literal:

   'WHERE active = true'
   

5. Ruby combines that too.

6. The final value of sql becomes:

   SELECT name, email FROM users WHERE active = true
   

7. puts sql prints the full combined string.

Heredoc trace

Now compare that with a heredoc:

Multi-line strings are common in real Ruby programs.

SQL queries

query = <<~SQL
  SELECT id, name, email
  FROM users
  WHERE active = true
  ORDER BY name
SQL

Used in:

• database scripts
• reporting tools
• background jobs
• Rails apps with raw SQL

HTML or email templates

html = <<~HTML
  <h1>Welcome</h1>
  <p>Your account is ready.</p>
HTML

Used in:

• email generation
• simple server responses
• templated notifications

JSON payloads

payload = <<~JSON
  {
    "event": "signup",
    "status": "success"
  }
JSON

Used in:

• API testing
• fixtures
• mock requests

Shell commands

command = <<~CMD
  echo "Starting"
  echo "Done"
CMD

Used in:

• automation scripts
• deployment helpers
• build tools

In real projects, developers usually choose the style that makes intent most obvious.

Common patterns

1. Heredoc for long SQL

sql = <<~SQL
  SELECT users.id, users.name
  FROM users
  WHERE users.active = true
SQL

This is common because SQL is easier to review when formatted like SQL.

2. Assign once, pass later

sql = <<~SQL
  SELECT *
  FROM orders
  WHERE status = 'pending'
SQL

result = conn.exec(sql)

This helps with:

• debugging
• logging
• testing
• reusing the query

3. Inline heredoc for one-off calls

conn.exec(<<~SQL)
  SELECT *
  FROM products
  WHERE in_stock = true
SQL

Good for short one-use queries.

4. Interpolation with care

table_name = 'users'
sql = <<~SQL
  SELECT *
  FROM #{table_name}
SQL

Useful, but developers should be careful with untrusted input. For values, parameterized queries are safer than building SQL manually.

5. Guarding readability

If a string becomes too long or complex, developers usually:

1. Using + everywhere

This works, but it is noisy and harder to maintain.

sql = 'SELECT * ' +
      'FROM users ' +
      'WHERE active = true'

Prefer:

sql = 'SELECT * ' 
      'FROM users ' 
      'WHERE active = true'

or a heredoc.

2. Forgetting spaces between string parts

Broken example:

sql = 'SELECT *'
      'FROM users'

This becomes:

SELECT *FROM users

Fix it by adding spaces where needed:

sql = 'SELECT * ' 
      'FROM users'

3. Confusing code newlines with string newlines

With adjacent literals:

sql = 'SELECT * ' 
      'FROM users'

The final string is:

Adjacent literals vs heredoc

Quick reference

Adjacent string literals

text = 'Hello, ' 
       'world'

• Ruby combines them into one string
• Good for long one-line output
• Remember spaces between parts if needed

Heredoc

text = <<~TEXT
  Hello
  world
TEXT

• Best for multi-line content
• Preserves line breaks
• <<~ removes common indentation

Backslash continuation

text = 'Hello, ' \
       'world'

• Continues an expression onto the next line
• Less readable than heredoc for large blocks

Interpolation rules

name = 'Ada'
text = "Hello, #{name}"

• Single quotes: no interpolation
• Double quotes: interpolation works
• Heredoc usually supports interpolation unless using a non-interpolating form

Good SQL style

sql = 

Can Ruby automatically concatenate strings on separate lines?

Yes. Adjacent string literals can be combined without +, as long as they are written as neighboring literals in a valid expression.

What is the cleanest way to write long SQL in Ruby?

Usually a heredoc, because it keeps the SQL readable and formatted like normal SQL.

Does a heredoc include newline characters?

Yes. A heredoc preserves line breaks inside the string.

If I do not want newline characters, should I still use a heredoc?

Usually no. If you want one flat string, adjacent string literals are often simpler.

Is + wrong for joining strings in Ruby?

No, but it is often less readable for long static strings.

Can I interpolate variables inside a multi-line Ruby string?

Yes, if you use double-quoted strings or an interpolating heredoc.

Are multi-line SQL strings safe?

The formatting style is safe, but interpolating untrusted values directly into SQL is not. Use parameterized queries for values.

What does <<~ mean in a heredoc?

It creates a heredoc and strips common indentation, which helps keep your Ruby code nicely indented.

• String literals — Multi-line strings are built from normal Ruby string literal rules.
• String interpolation — Useful when inserting Ruby values into a string.
• Heredoc — The main Ruby feature for readable blocks of text.
• Escape sequences — Important when you need explicit newlines like \n.
• SQL in Ruby — Long strings often appear when writing raw SQL queries.
• Parameterized queries — Related because long SQL strings often need safe value insertion.
• Single vs double quotes in Ruby — Affects interpolation and string behavior.
• String concatenation — The alternative approach this question is trying to avoid.