Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitf890004

Browse files
committed
Update sequence docs.
1 parentf20cad7 commitf890004

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

‎doc/src/sgml/release.sgml

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.383 2005/10/03 02:21:16 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.384 2005/10/03 02:46:43 momjian Exp $
33

44
Typical markup:
55

@@ -398,28 +398,28 @@ pg_[A-Za-z0-9_] <application>
398398
</para>
399399
<para>
400400
In previous releases, <function>nextval()</>,
401-
<function>currval</>, and <function>setval()</> recorded
402-
sequencenames as simple text strings, meaning that renaming or
403-
dropping asequence used in a <command>DEFAULT</> made the
404-
clauseinvalid. This release stores all newly-created sequence
405-
functionargumentsusing internal OIDs, allowing them to handle
406-
sequencerenaming, and adding dependency information that
407-
preventsimproper sequence removal. It also makes
408-
<command>DEFAULT</>clauses immune to schema search
409-
path changes.
401+
<function>currval</>, and <function>setval()</> recorded sequence
402+
names as simple text strings, meaning that renaming or dropping a
403+
sequence used in a <command>DEFAULT</>clausemade the clause
404+
invalid. This release stores all newly-created sequence function
405+
argumentsas internal OIDs, allowing them to handle sequence
406+
renaming, and adding dependency information that prevents
407+
improper sequence removal. It also makes <command>DEFAULT</>
408+
clauses immune to schema search path changes, and allows schema
409+
renaming.
410410
</para>
411411
<para>
412412
Some applications might rely on the old text-based behavior of
413-
run-time lookupof thesequencename. This can still be done by
413+
run-time lookupforsequencenames. This can still be done by
414414
casting the argument to <type>text</>, for example
415415
<literal>nextval('myseq'::text)</>.
416416
</para>
417417
<para>
418418
Pre-8.1 schemas loaded into 8.1 will use the previous, text-based
419-
representation and therefore will not havethese protections.
420-
However, it is possible to upgrade a database to the newer
421-
OID-based arguments. First, save this query into a file, such as
422-
<filename>fixseq.sql</>:
419+
representation and therefore will not havethe features of
420+
OID-stored arguments.However, it is possible to upgrade a
421+
database loaded with pre-8.1 schemas. First, save this query into
422+
a file, such as<filename>fixseq.sql</>:
423423
<programlisting>
424424
SELECT 'ALTER TABLE ' ||
425425
pg_catalog.quote_ident(n.nspname) || '.' ||

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp