On 04/19/2012 04:55 AM, Dennis wrote:
Hello Tom,
The example you have given is EXACTLY why something like CURRENT is
needed to limit the number of unique queries or prepared statements. (or
to do a selection of all values before an update meaning two executed
queries.)
regards,.
Dennis
On 04/
Hello Tom,
The example you have given is EXACTLY why something like CURRENT is needed to limit the number of
unique queries or prepared statements. (or to do a selection of all values before an update meaning
two executed queries.)
regards,.
Dennis
On 04/18/2012 06:24 PM, Tom Lane wrote:
D
Dennis writes:
> When a query is written to update a table, the usual process is to list all
> the columns that need
> updating. This could imply the creation of many possible queries for many
> columns. In an effort to
> keep the UPDATE queries more uniform, less number of unique queries, a
On 04/18/2012 04:11 AM, Dennis wrote:
When a query is written to update a table, the usual process is to list
all the columns that need updating. This could imply the creation of
many possible queries for many columns. In an effort to keep the UPDATE
queries more uniform, less number of unique qu
When a query is written to update a table, the usual process is to list all the columns that need
updating. This could imply the creation of many possible queries for many columns. In an effort to
keep the UPDATE queries more uniform, less number of unique queries, a keyword similar to DEFAULT,
