| Age | Commit message (Collapse) | Author |
|
|
|
|
|
elements prior to CREATEing new ones. It is under control of the -c
command line option (with the default being status quo).
The DROP TRIGGER portion still needs implementation. Anyone able to
help clarify what exactly the CREATE TRIGGER portion does so I can fix
this?
Again, I have tried this with tables/indexes/sequences, but do not
have other schema elements in my database. As a result, I am not 100%
convinced that I got the syntax correct in all cases (but think I did,
nonetheless). If anyone can check the other cases, I'd appreciate it.
Cheers,
Brook
[I added manual page and sgml additions for the new -c option.]
|
|
|
|
|
|
the User's Guide sometime soon.
|
|
Include info for time zones, days of week, months.
Procedural description of date input parsing is not yet complete.
|
|
file. Per Bruce's preference. Go to it Bruce!
No info yet for v6.4.2 or upcoming releases.
|
|
|
|
which was not built last time these things changed.
|
|
|
|
|
|
Use a <citetitle> rather than <xref> when referring to libpq
since that chapter is not included in the tutorial.
|
|
which are not used here.
|
|
|
|
|
|
From Magnus Hagander <mha@sollentuna.net>.
|
|
of Norm's Modular Style Sheets and jade/docbook.
From Vince Vielhaber <vev@michvhf.com>.
|
|
Please apply to both trees.
--
Tatsuo Ishii
|
|
Add Emacs configuration block to postgres.sgml.
|
|
the FROM clause. e.g. "SELECT table.*".
|
|
These fixes are from Jeff Hoffmann <jeff@remapcorp.com>.
|
|
Remove mention of the old "migration" flat files.
Change URLs for resources to point to areas, not particular files.
That way things stay correct even when version of tools change.
Suggested by Vince Vielhaber.
|
|
Rearrange a few other keywords to put them in the proper category.
|
|
|
|
|
|
tags even if DocBook is not installed on your local system.
Most of the .sgml source files contain a reference to this file in an
Emacs setup block at the bottom of the file...
|
|
Not yet complete, integrated, or marked up.
Not yet included in a document (should go in the developer's doc?).
|
|
6.4.1. Here is the list:
- The type int8 now works. In fact, the bug(s) were in
src/backend/port/snprintf.c, so int8 is probably broken in every platform
that hasn't a native snprintf/vsnprintf. The type itself worked as
expected, only the output was wrong. Anyway, this patch should be checked
in other platforms.
- The regression tests for int2 and int4, which were broken due to
differences in the error messages, are fixed.
- The regression test for float8, which was broken in the reference
platform, is also fixed. I don't know if the new file (float8-OSF1.out)
will work on other platforms, but it might be worth to try it.
- Two new template files are provided (alpha_cc, which includes
optimization, and alpha_gcc), and src/templates/.similar is updated
accordingly. src/templates/alpha should be removed from the distribution.
*IMPORTANT NOTE*: I don't know if you can use gcc to compile postgres;
I've written the alpha_gcc file because alpha_cc has some flags that are
specific to DEC C.
- There is a (very basic) Digital Unix specific FAQ in
doc/FAQ_DigitalUnix.
--
-------------------------------------------------------------------
Pedro José Lobo Perea Tel: +34 91 336 78 19
|
|
html and man.
|
|
|
|
instead of relying on port's os.h to tell us. (Needed for HPUX
where system major version is not enough info.)
configure unsets USE_TK if X libraries not found.
doc/Makefile uses gzcat or zcat as found by autoconf.
|
|
|
|
|
|
|
|
Fix missing mention of "-n" flag in synopsis.
|
|
vaccumdb reference page.
|
|
|
|
|
|
|
|
Include only the current release in the release notes section.
|
|
Already in product docs since they were built on my machine.
|
|
Make new file current.sgml to hold release info for the current release.
Should be moved to release.sgml before filling with next release info.
|
|
Was picking up subdirectories and other garbage.
|
|
|
|
documentation for v6.4.
Bigger updates to the installation instructions (install and config).
|
|
|
|
|
|
in a year an a half. Much of the info was wrong and is covered more
correctly elsewhere.
|
|
Postgres is missing a procedural language. He correctly points out
that we now have two (thanks to him, but he modestly didn't mention
that).
|