Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Using <code>EXECUTE ... USING</code> with the <code>format()</code> function and its format specifiers will make your code much safer, simpler, easier to read and probably faster.</p> <hr> <p><strong>SQL INJECTION WARNING</strong>: If you ever accept <code>source_geom</code> or <code>target_geom</code> from the end user, your code is potentially vulnerable to <a href="http://bobby-tables.com/postgresql.html" rel="noreferrer">SQL injection</a>. It is important to use parameterized statements (like <code>EXECUTE ... USING</code>) or failing that, paranoid quoting to prevent SQL injection attacks. Even if you don't think your function takes user input you should still harden it against SQL injection, because you don't know how your app will evolve.</p> <hr> <p>If you're on a newer PostgreSQL with the <a href="http://www.postgresql.org/docs/current/static/functions-string.html" rel="noreferrer"><code>format</code> function</a> your code can be significantly simplified into:</p> <pre><code>EXECUTE format('update %I SET source = %L, target = %L WHERE %I = %L', geom_table, source_geom, target_geom, gid_cname, _r.id); </code></pre> <p>... which handles identifier (<code>%I</code>) and literal (<code>%L</code>) quoting for you using format specifiers so you don't have to write all that awful <code>||</code> concatenation and <code>quote_literal</code>/<code>quote_ident</code> stuff.</p> <p>Then, as per <a href="http://www.postgresql.org/docs/9.1/static/plpgsql-statements.html#PLPGSQL-QUOTE-LITERAL-EXAMPLE" rel="noreferrer">the documentation on <code>EXECUTE ... USING</code></a> you can further refine the query into:</p> <pre><code>EXECUTE format( 'update %I SET source = $1, target = $2 WHERE %I = $3', geom_table, gid_cname ) USING source_geom, target_geom, _r.id; </code></pre> <p>which turns the query into a parameterised statement, clearly separating parameters from identifiers and reducing string processing costs for a more efficient query.</p>
    singulars
    1. This table or related slice is empty.
    1. POCorrectly inserting literals in PL/PgSQL EXECUTE dynamic queries
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCraig Ringer
    1. USCraig Ringer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COEXECUTE format('...') USING is probably best. A parameters in format function should be used when cannot be used in USING clause - column, table names.
      singulars
      1. PO
      1. USPavel Stehule
 

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