Databases
StackOverflow2013
Postsdbo
POPython SQL query string formatting
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPython SQL query string formatting
    primarykey
    data
    text
    <p>I'm trying to find the best way to format an sql query string. When I'm debugging my application I'd like to log to file all the sql query strings, and it is important that the string is properly formated.</p> <p><strong>Option 1</strong></p> <pre><code>def myquery(): sql = "select field1, field2, field3, field4 from table where condition1=1 and condition2=2" con = mymodule.get_connection() ... </code></pre> <ul> <li>This is good for printing the sql string.</li> <li>It is not a good solution if the string is long and not fits the standard width of 80 characters.</li> </ul> <p><strong>Option 2</strong></p> <pre><code>def query(): sql = """ select field1, field2, field3, field4 from table where condition1=1 and condition2=2""" con = mymodule.get_connection() ... </code></pre> <ul> <li><p>Here the code is clear but when you print the sql query string you get all these annoying white spaces.</p> <blockquote> <p>u'\nselect field1, field2, field3, field4\n_<strong><em>_</em>___</strong><em>from table\n</em><strong><em>_</em>___</strong><em>where condition1=1 \n</em><strong><em>_</em>___</strong>_and condition2=2'</p> </blockquote></li> </ul> <p><em>Note: I have replaced white spaces with underscore <code>_</code>, because they are trimmed by the editor</em></p> <p><strong>Option 3</strong></p> <pre><code>def query(): sql = """select field1, field2, field3, field4 from table where condition1=1 and condition2=2""" con = mymodule.get_connection() ... </code></pre> <ul> <li>I don't like this option because it breaks the clearness of the well tabulated code.</li> </ul> <p><strong>Option 4</strong></p> <pre><code>def query(): sql = "select field1, field2, field3, field4 " \ "from table " \ "where condition1=1 " \ "and condition2=2 " con = mymodule.get_connection() ... </code></pre> <ul> <li>I don't like this option because all the extra typing in each line and is difficult to edit the query also.</li> </ul> <p>For me the best solution would be <strong>Option 2</strong> but I don't like the extra whitespaces when I print the sql string.</p> <p>Do you know of any other options?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDouglas
    1. USssoler
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPython SQL query string formatting
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPython SQL query string formatting
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPython SQL query string formatting
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is what the Psycopg people call a a naïve approach to the composition of query strings, e.g. using string concatenation - http://initd.org/psycopg/docs/usage.html#the-problem-with-the-query-parameters . Instead use query parameters to avoid SQL injection attacks and to automatically convert Python objects to and from SQL literals. http://stackoverflow.com/questions/3134691/python-string-formats-with-sql-wildcards-and-like?rq=1#comment24606225_3134691
      singulars
      1. POPython SQL query string formatting
      1. USMatthew Cornell
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload