Commit Graph

240 Commits

Author SHA1 Message Date
Tom Lane 52200befd0 Implement types regprocedure, regoper, regoperator, regclass, regtype
per pghackers discussion.  Add some more typsanity tests, and clean
up some problems exposed thereby (broken or missing array types for
some built-in types).  Also, clean up loose ends from unknownin/out
patch.
2002-04-25 02:56:56 +00:00
Thomas G. Lockhart b76b6f61b0 Minor wording change for readability. 2002-04-21 18:58:00 +00:00
Bruce Momjian e916ad28c7 Mention precision of NUMERIC in docs. 2002-04-13 01:35:09 +00:00
Peter Eisentraut 867901db9e Locale support is on by default. The choice of locale is done in initdb
and/or with GUC variables.
2002-04-03 05:39:33 +00:00
Peter Eisentraut b6ea172ace Spell checking and markup additions 2002-03-22 19:20:45 +00:00
Bruce Momjian 7bf7b0bd75 This trivial patch fixes a typo and improves the phrasing of a sentence
in the docs.

Neil Conway
2002-03-05 06:14:45 +00:00
Peter Eisentraut bf43bed848 Spell-check and markup police 2002-01-20 22:19:57 +00:00
Peter Eisentraut 731204e090 Editorial review 2002-01-07 02:29:15 +00:00
Thomas G. Lockhart c5c28ed06a Add more complete details on date/time keywords and parsing rules.
Move some tabular information on these from the chapter on data types to
 the appendix on dates and times.
2002-01-04 17:02:25 +00:00
Thomas G. Lockhart dd0279b1ba Document the precision arguments for date/time types per SQL9x.
Update the list of recognized time zones.
Document the range of arguments allowed for SET TIME ZONE.
Still need to add info on other date/time symbols (e.g. "AM", "T")
 and to freshen the docs on the date/time parsing rules.
2001-12-29 18:35:54 +00:00
Tom Lane 78ec1cb027 Type interval takes a precision, too. 2001-12-23 20:21:37 +00:00
Thomas G. Lockhart 9640666c6f Spiff up discussion of precision on date/time data types.
Add a NetBSD/alpha and update info on a few other platforms.
2001-12-21 03:54:02 +00:00
Thomas G. Lockhart 68cb184b56 Update list of currently supported platforms.
Mention SQL9x precision syntax for date/time types.
Use PostgreSQL consistantly throughout docs. Before, usage was split evenly
 between Postgres and PostgreSQL.
2001-12-08 03:24:23 +00:00
Peter Eisentraut 651a639b8b proof-reading 2001-11-28 20:49:10 +00:00
Tom Lane 2ec958721d Tweak int8in to accept -9223372036854775808, per recent discussion in
pgsql-patches.
2001-11-24 19:57:06 +00:00
Tom Lane 22e22a5208 Spelling and grammatical corrections. 2001-11-21 21:12:34 +00:00
Thomas G. Lockhart 2475e87481 Deprecate 'current' for date/time input.
Fix up references to "PostgreSQL" rather than "Postgres". Was roughly
 evenly split between the two before. ref/ files not yet done.
2001-11-21 05:53:41 +00:00
Bruce Momjian 8e6467fff3 Peter Eisentraut wrote:
> So I would base this discussion on the premise "bytea stores binary data"
> (insert examples).
>
> Some stylistic issues:
>
> bytea => <type>bytea</type>
>
> NULLs => zero bytes/bytes of value zero ("NULL" is too overloaded)
>
> 'non-printable' => <quote>nonprintable</quote>
>
> MUST => <emphasis>must</emphasis>
>

Here's a patch against *CVS tip* to address Peter's comments. Please let
me know what you think!

Joe Conway
2001-11-21 03:17:22 +00:00
Bruce Momjian 01e0dae689 I've created a new section to func.sgml, "Binary String Functions and
Operators", plagiarized shamelessly from the "String Functions and
Operators" section. There were enough differences that it made sense (at
least to me) to give this its own section instead of cramming it in with
normal string functions. This way I could also make the examples
relevant, which is particularly important for bytea.

One thing I think worth mentioning: while documenting the trim()
function I realized that I never implemented the bytea equivalent of
rtrim and ltrim. Therefore, the 'leading' and 'trailing' forms of trim,
available with text, are not available with bytea (I'd be happy to
correct this, but since it would require an initdb, I guess not until
7.3) -- the submitted doc accurately reflects this.

I will look for other areas of the docs that need mention of bytea, but
any guidance would be much appreciated.

--

Here's a second bytea documentation patch. This one significantly
expands the "Binary Data" section added by Bruce recently.


Joe Conway
2001-11-20 15:42:44 +00:00
Tom Lane 5e86d226e4 Grammatical and spelling fixes. 2001-11-19 09:05:02 +00:00
Tom Lane 9b03776ff2 A bunch of small doco updates motivated by scanning the comments on
the interactive docs.
2001-11-19 03:58:25 +00:00
Tom Lane a585c20d12 Tweak parser so that there is a defined representation for datatypes
bpchar, bit, numeric with typmod -1.  Alter format_type so that this
representation is printed when the typmod is -1.  This ensures that
tables having such columns can be pg_dump'd and reloaded correctly.
Also, remove the rather useless and non-SQL-compliant default
precision and scale for type NUMERIC.  A numeric column declared as
such (with no precision/scale) will now have typmod -1 which means
that numeric values of any precision/scale can be stored in it,
without conversion to a uniform scale.  This seems significantly
more useful than the former behavior.  Part of response to bug #513.
2001-11-12 21:04:46 +00:00
Peter Eisentraut 06f008e154 Spacing improvements 2001-11-08 23:36:55 +00:00
Tom Lane b9cd4c8331 Grammatical corrections. 2001-10-30 20:13:44 +00:00
Peter Eisentraut ffb8f73890 Bunch of copy fitting and style sheet tweakage to get decent looking print
output (from pdfjadetex).  Also updated instructions to install documentation
processing toolchain.
2001-10-09 18:46:00 +00:00
Thomas G. Lockhart a51de40fb6 Minor fixup in spacing for tabular information. 2001-10-03 05:24:22 +00:00
Thomas G. Lockhart f9681968e0 Add information on new timestamp and timestamptz data types.
Start chapter on recovery techniques. Still needs work for release.
2001-09-28 08:15:35 +00:00
Peter Eisentraut 351a0c1736 Replace ASCII-quotes with proper markup. 2001-09-13 15:55:24 +00:00
Peter Eisentraut 84956e71a3 Markup additions and spell check. (covers User's Guide) 2001-09-09 17:21:59 +00:00
Bruce Momjian 9b77572662 Add mention of bytea data type and escaping rules. 2001-09-04 03:17:54 +00:00
Tatsuo Ishii 94427b1914 Since 7.1 the data type size of TIME has been increased. 2001-08-31 01:55:25 +00:00
Peter Eisentraut 9cf701f324 Start adding some more documentation about the number types. Make
bigserial and alias for serial8 for consistency with bigint/int8.
2001-08-24 20:03:45 +00:00
Tom Lane d4f4b971a4 Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type
has an alias SERIAL4 and a sister SERIAL8.  SERIAL8 is just the same
except the created column is type int8 not int4.
initdb forced.  Note this also breaks any chance of pg_upgrade from 7.1,
unless we hack up pg_upgrade to drop and recreate sequences.  (Which is
not out of the question, but I don't wanna do it.)
2001-08-16 20:38:56 +00:00
Peter Eisentraut e29c16dc50 some clarifications inspired by the DocNotes 2001-08-07 22:41:49 +00:00
Tom Lane ec96f1dacd Fix some references to USE_AUSTRALIAN_RULES that Bruce missed;
plus a few trivial improvements in wording.
2001-06-18 19:05:11 +00:00
Peter Eisentraut efcecd9eca Make bit and bit varying types reject too long input. (They already tried
to do that, but inconsistently.)  Make bit type reject too short input,
too, per SQL.  Since it no longer zero pads, 'zpbit*' has been renamed to
'bit*' in the source, hence initdb.
2001-05-22 16:37:17 +00:00
Peter Eisentraut 5546ec289b Make char(n) and varchar(n) types raise an error if the inserted string is
too long.  While I was adjusting the regression tests I moved the array
things all into array.sql, to make things more manageable.
2001-05-21 16:54:46 +00:00
Peter Eisentraut 01839df6dd Add index. Only some parts of the manual set have index entries so far... 2001-05-12 22:51:36 +00:00
Peter Eisentraut 0967057b5d minor copy editing 2001-03-24 23:03:26 +00:00
Tom Lane af129857c4 BOX documentation disagreed with code about corner order. 2001-03-10 21:16:32 +00:00
Peter Eisentraut d42d31e78e Alter documentation of boolean type, add example. Someone figured that it
wasn't clear that the "boolean type" was actually called "boolean".  Add
tip about "casting" booleans using CASE.

Spell check whole file.
2001-02-14 19:37:26 +00:00
Peter Eisentraut 88517a2d9e Add note about the availability of contrib/mac for the macaddr data type. 2001-02-10 18:02:35 +00:00
Peter Eisentraut 61737a7b47 Add some links from data type chapter to section on literal constants. 2001-01-26 22:04:22 +00:00
Peter Eisentraut 526427f6d3 Add information about bit types. Adjust some other things to promote
SQL type names over internal type names.
2001-01-13 18:34:51 +00:00
Peter Eisentraut 1b555ce791 Replace incorrect uses of 'which' with 'that'. (so-called "wicked which") 2000-12-22 18:57:50 +00:00
Tom Lane 61784c54b5 Change default output formatting for CIDR to be unabbreviated, per
recommendation from Paul Vixie.  Add a new abbrev() function to produce
abbreviated format as text.  No forced initdb, but new function is not
available unless you do an initdb or add the pg_proc row manually.
2000-12-22 18:00:24 +00:00
Peter Eisentraut c3641483c3 Merge functions and operators chapters. Lots of updates. 2000-12-14 22:30:56 +00:00
Thomas G. Lockhart 1131261270 Clarify the allowed length of the text data type. 2000-12-03 14:47:18 +00:00
Bruce Momjian 5a0152b3fd I think in datatype.sgml line 506 or so:
<entry>varchar(n)</entry>
        <entry>(4+x) bytes</entry>

should be
   <entry>varchar(n)</entry>
        <entry>(4+n) bytes</entry>

or
   <entry>varchar(x)</entry>
        <entry>(4+x) bytes</entry>

Regards

Laser Henry
2000-11-16 06:03:40 +00:00
Peter Eisentraut 609f9199af Repair markup 2000-11-11 23:27:48 +00:00
Thomas G. Lockhart ecc367b764 Mention new AT TIME ZONE feature. 2000-11-11 19:50:31 +00:00
Tom Lane a210023008 Adjust INET/CIDR display conventions and reimplement some INET/CIDR
functions, per recent discussions on pghackers.  For now, I have called
the verbose-display formatting function text(), but will reconsider if
enough people object.
initdb forced.
2000-11-10 20:13:27 +00:00
Peter Eisentraut baa3a09b5f Convert macaddr documentation to DocBook, update outdated information. 2000-10-04 15:47:45 +00:00
Peter Eisentraut 72ad5fe15c Add `id' attributes to all `chapter' and `sect1' tags, to generate useful
names for the HTML files (e.g., not x4856.htm).
2000-09-29 20:21:34 +00:00
Peter Eisentraut 457ac0331c Implement differentiation between CURRENT_USER and SESSION_USER as per SQL.
There is still no effective difference but it will kick in once setuid
functions exist (not included here).  Make old getpgusername() alias for
current_user.
2000-09-19 18:18:04 +00:00
Bruce Momjian 67cd018e77 Startup is actually start-up. 2000-08-29 20:02:09 +00:00
Tom Lane 0813fcbc08 Documentation updates to reflect TOAST and new-style fmgr. 2000-08-24 23:36:29 +00:00
Thomas G. Lockhart 2b6a35f7cd Fix several <ulink> tags which refer to e-mail addresses
but were missing the "mailto:" prefix.
Fix typo.
Thanks to Neil Conway <nconway@klamath.dyndns.org> for the heads-up.
2000-08-23 05:59:11 +00:00
Tom Lane d70d46fd60 PATH and POLYGON datatypes are now TOASTable. Associated functions
updated to new fmgr style.  Deleted hoary old functions for compatibility
with pre-6.1 representations of these datatypes.
2000-07-29 18:46:12 +00:00
Thomas G. Lockhart 4835f6a8bc Update docs for TIME WITHOUT TIME ZONE.
Add information on SET SESSION CHARACTERISTICS.
Fix references to pg_hba.conf(5) since that is no longer a man page.
2000-07-14 15:26:21 +00:00
Thomas G. Lockhart 45f79cae14 Fixups in content and markup for 7.0 release. 2000-05-02 20:02:03 +00:00
Thomas G. Lockhart b27cef2932 Mention support for date_part('week',timestamp).
Fix spelling of "millennium".
 Thanks to Mika Nystrom <mika@camembert.cs.caltech.edu>.
2000-04-14 15:08:56 +00:00
Bruce Momjian 2e67ecaf6f Change DEFINE TYPE to CREATE TYPE. 2000-04-13 21:44:25 +00:00
Bruce Momjian d57046097a Update for default ISO date style 2000-04-11 03:56:19 +00:00
Thomas G. Lockhart 73d8bbc2ac Minor markup changes. Refer to (".../catalog") in the emacs hints. 2000-03-31 03:27:42 +00:00
Peter Eisentraut 4579e68db2 Updated user's guide to match new psql's output format
Fixed bug in createdb/alternative location
2000-03-26 18:32:30 +00:00
Thomas G. Lockhart ce543b2121 Write up new TIME WITH TIME ZONE type. 2000-03-14 22:52:53 +00:00
Peter Eisentraut 49581f9848 updated install file
updated date/time types doc
fixed small psql bug
removed libpq code that lower-cased db names
make notice when long identifier is truncated
2000-01-23 01:27:39 +00:00
Bruce Momjian e3dd4942c7 Update for NUMERIC/DECIMAL data type. 1999-10-13 02:44:23 +00:00
Thomas G. Lockhart 4f1766f1ea Try to clarify characteristics of the SERIAL type.
Fix source indenting, which does not affect output.
Note: still need docs on NUMERIC and DECIMAL
 (and let's not talk about regression tests :()
1999-08-06 13:43:42 +00:00
Thomas G. Lockhart 5e84d58e70 Minor updates for release. 1999-06-14 07:36:12 +00:00
Thomas G. Lockhart b04b01638b Remove disclaimer about exact numeric types. They work now! 1999-05-27 15:47:28 +00:00
Thomas G. Lockhart 9474dd7ed6 Add chapters on CVS access, MVCC, SQL theory to the docs.
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
 *except* for the porting list which will require a report
 from a successful installation to be updated.
1999-05-26 17:30:30 +00:00
Thomas G. Lockhart 95e3cec621 Include mention of CASE, COALESCE, and IFNULL.
Add date/time parsing procedure (perhaps should be in appendix).
Add time zone information (ditto).
Update keyword list.
1999-05-12 07:32:47 +00:00
Thomas G. Lockhart 1def28ff20 Include specific info on available timezones.
Document date/time input parsing procedure.
1999-05-04 02:22:13 +00:00
Thomas G. Lockhart 7fcbc5ddf0 Fix markup to include all closing tags.
Required by newest versions of DocBook and style sheets.
1999-04-06 15:41:20 +00:00
Bruce Momjian cd72d24e02 bool uses one byte 1999-03-15 15:00:08 +00:00
Thomas G. Lockhart af2a0dfd65 Describe the date/time parsing rules.
Include specific information on the supported time zones.
 It's a really big table, so maybe it should go into an appendix instead.
1999-02-13 03:42:10 +00:00
Thomas G. Lockhart c00d800e2d Add tables of allowed values and formats for date/time input types.
Include info for time zones, days of week, months.
Procedural description of date input parsing is not yet complete.
1999-01-19 16:08:26 +00:00
Thomas G. Lockhart 4bbcad1ee0 Update some info, especially the CIDR/INET data types. 1998-12-18 16:11:12 +00:00
Thomas G. Lockhart f1f9ec3344 Minor editing and markup changes as a result of preparing the Postscript
documentation for v6.4.
Bigger updates to the installation instructions (install and config).
1998-10-30 19:37:19 +00:00
Thomas G. Lockhart e9f10b22f4 Include new cidr and inet data types. 1998-10-27 06:14:41 +00:00
Thomas G. Lockhart 3103a05c64 Add mention of the SERIAL data type.
Change claim of "no limit" on maximum date for datetime type to
 more realistic 1465001 AD. Thanks Tatsuo for pointing this out :)
Clean up markup.
1998-10-14 16:26:31 +00:00
Thomas G. Lockhart 0463ee00ae Fix small typo. 1998-08-17 16:12:35 +00:00
Thomas G. Lockhart 5f372f9e59 Add id field to chapter and book tags to allow output file names
to be meaningful.
1998-07-29 06:50:04 +00:00
Thomas G. Lockhart ba3a99f193 Split function and operator User Guide info
from datatype.sgml into separate files.
Add type conversion information.
Format historical release notes.
1998-07-08 13:53:15 +00:00
Bruce Momjian d31736e92b Doc updates from Darren on char2-16 removal 1998-04-26 04:18:06 +00:00
Thomas G. Lockhart a0ca95fa0d Fix typos in a couple of examples. 1998-04-17 03:55:01 +00:00
Thomas G. Lockhart 90dbfa5ea6 Fix a few typos. Try <Note><Title>Author</Title>... for author credit. 1998-03-01 20:46:10 +00:00
Thomas G. Lockhart c8cfb0cea8 SGML source for new documentation. 1998-03-01 08:16:16 +00:00