Commit b351eba2 authored by Tom Lane's avatar Tom Lane

Add comment about the two different query strings that ExecuteQuery()

has to deal with.
parent 5618ece8
...@@ -10,7 +10,7 @@ ...@@ -10,7 +10,7 @@
* Copyright (c) 2002-2008, PostgreSQL Global Development Group * Copyright (c) 2002-2008, PostgreSQL Global Development Group
* *
* IDENTIFICATION * IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/commands/prepare.c,v 1.88 2008/07/18 20:26:06 tgl Exp $ * $PostgreSQL: pgsql/src/backend/commands/prepare.c,v 1.89 2008/07/21 15:26:55 tgl Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
...@@ -162,6 +162,12 @@ PrepareQuery(PrepareStmt *stmt, const char *queryString) ...@@ -162,6 +162,12 @@ PrepareQuery(PrepareStmt *stmt, const char *queryString)
/* /*
* Implements the 'EXECUTE' utility statement. * Implements the 'EXECUTE' utility statement.
*
* Note: this is one of very few places in the code that needs to deal with
* two query strings at once. The passed-in queryString is that of the
* EXECUTE, which we might need for error reporting while processing the
* parameter expressions. The query_string that we copy from the plan
* source is that of the original PREPARE.
*/ */
void void
ExecuteQuery(ExecuteStmt *stmt, const char *queryString, ExecuteQuery(ExecuteStmt *stmt, const char *queryString,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment