postgresql/src/interfaces/ecpg
Tom Lane c252a17d82 Rename frontend keyword arrays to avoid conflict with backend.
ecpg and pg_dump each contain keyword arrays with structure similar
to the backend's keyword array.  Up to now, we actually named those
arrays the same as the backend's and relied on parser/keywords.h
to declare them.  This seems a tad too cute, though, and it breaks
now that we need to PGDLLIMPORT-decorate the backend symbols.
Rename to avoid the problem.  Per buildfarm.

(It strikes me that maybe we should get rid of the separate keywords.c
files altogether, and just define these arrays in the modules that use
them, but that's a rather more invasive change.)
2012-03-31 13:15:53 -04:00
..
compatlib Update copyright notices for year 2012. 2012-01-01 18:01:58 -05:00
ecpglib Add missing va_end() calls 2012-03-14 22:47:21 +02:00
include Mark variables as const in pgtypeslib if they only carry a format string. 2011-12-18 19:04:19 +01:00
pgtypeslib Add const qualifier to tzn returned by timestamp2tm() 2012-03-15 21:17:19 +02:00
preproc Rename frontend keyword arrays to avoid conflict with backend. 2012-03-31 13:15:53 -04:00
test Make sure all connection paramters are used in call to PQconnectdbParams. 2012-02-18 14:18:16 +01:00
Makefile De-parallelize ecpg build some more. 2011-10-28 15:16:40 -04:00
README.dynSQL Remove useless whitespace at end of lines 2010-11-23 22:34:55 +02:00

src/interfaces/ecpg/README.dynSQL

descriptor statements have the following shortcomings

- input descriptors (USING DESCRIPTOR <name>) are not supported

  Reason: to fully support dynamic SQL the frontend/backend communication
  	should change to recognize input parameters.
  	Since this is not likely to happen in the near future and you
  	can cover the same functionality with the existing infrastructure
  	(using s[n]printf), I'll leave the work to someone else.