| Age | Commit message (Collapse) | Author |
|---|
|
Zoltan <zb@cybertec.at>.
|
|
[OUTPUT] statement to ecpg.
|
|
Given that undefined types are handled as character strings anyway the type
translation function can simply return the correcponding ECPGt_char type.
|
|
For non-SQL3 types ecpg used to return -Oid. This will break if there are
enough Oids to fill the namespace. Therefore we play it safe and return 0 if
there is no Oid->SQL3 tyoe mapping available.
|
|
isn't actively used anymore.
|
|
|
|
we're not going to support that anymore.
I did keep the 64-bit-CRC-with-32-bit-arithmetic code, since it has a
performance excuse to live. It's a bit moot since that's all ifdef'd
out, of course.
|
|
|
|
|
|
OS specific with some distinguishing between signaling and quiet nans. It's not
really importnat for us here anyway.
|
|
|
|
superfluous include files.
|
|
|
|
|
|
|
|
forgot about the cvs stuff.
|
|
|
|
|
|
|
|
ecpg in both native and compatiblity mode.
|
|
pg_attribute, by having genbki.pl derive the information from the various
catalog header files. This greatly simplifies modification of the
"bootstrapped" catalogs.
This patch finally kills genbki.sh and Gen_fmgrtab.sh; we now rely entirely on
Perl scripts for those build steps. To avoid creating a Perl build dependency
where there was not one before, the output files generated by these scripts
are now treated as distprep targets, ie, they will be built and shipped in
tarballs. But you will need a reasonably modern Perl (probably at least
5.6) if you want to build from a CVS pull.
The changes to the MSVC build process are untested, and may well break ---
we'll soon find out from the buildfarm.
John Naylor, based on ideas from Robert Haas and others
|
|
|
|
This is more in keeping with modern practice, and is a first step towards
porting to Win64 (which has sizeof(pointer) > sizeof(long)).
Tsutomu Yamada, Magnus Hagander, Tom Lane
|
|
|
|
|
|
|
|
found and solved by Boszormenyi Zoltan <zb@cybertec.at>, some small adjustments
by me.
|
|
comment.
|
|
string too.
|
|
in the build process. If not the build process will stop with an error message.
|
|
|
|
|
|
|
|
Boszormenyi Zoltan, with only a minor tweak or two from me.
|
|
|
|
newline representations. Per buildfarm results and subsequent discussion.
Sync up a couple of other places that had their own policies.
|
|
list, minus a few specific words that have to be treated specially. This
replaces a hard-wired list of keywords that would have needed manual
maintenance, and was not getting it. The 8.4 coding was already missing
these words, causing ecpg to incorrectly treat them as reserved words:
CALLED, CATALOG, DEFINER, ENUM, FOLLOWING, INVOKER, OPTIONS, PARTITION,
PRECEDING, RANGE, SECURITY, SERVER, UNBOUNDED, WRAPPER. In HEAD we were
additionally missing COMMENTS, FUNCTIONS, SEQUENCES, TABLES.
Per gripe from Bosco Rama.
|
|
This is a preparatory patch for allowing a dynamic cursor name be used in the
ECPG grammar.
Author: Zoltan Boszormenyi
|
|
The main motivation for this is that it's required for Informix compatibility
in ECPG.
This patch makes the ECPG and core grammars a bit closer to one another for
these productions.
Author: Zoltan Boszormenyi
|
|
it works just as well to have them be ordinary identifiers, and this gets rid
of a number of ugly special cases. Plus we aren't interfering with non-rule
usage of these names.
catversion bump because the names change internally in stored rules.
|
|
files in one run.
|
|
|
|
patch send in by Boszormenyi Zoltan <zb@cybertec.at>.
|
|
decimal handling.
|
|
Zoltan Boszormenyi <zb@cybertec.at>.
|
|
to create a function for it.
Procedural languages now have an additional entry point, namely a function
to execute an inline code block. This seemed a better design than trying
to hide the transient-ness of the code from the PL. As of this patch, only
plpgsql has an inline handler, but probably people will soon write handlers
for the other standard PLs.
In passing, remove the long-dead LANCOMPILER option of CREATE LANGUAGE.
Petr Jelinek
|
|
function that returns the current transaction status.
|
|
rule in pgc.l.
|
|
It seems the flex developers have decided to change yyleng from int to size_t.
This has already happened in the latest release of OS X, and will start
happening elsewhere once the next release of flex appears. Rather than trying
to divine how it's declared in any particular build, let's just remove the one
existing not-very-necessary external usage.
Back-patch to all supported branches; not so much because users in the field
are likely to care about building old branches with cutting-edge flex, as
to keep OSX-based buildfarm members from having problems with old branches.
|
|
|
