Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
8fc97e82
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
8fc97e82
编写于
3月 20, 2000
作者:
T
Tom Lane
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Sorry, I have read the misspelling 'coersion' one time too many.
上级
b9a990d8
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
10 addition
and
10 deletion
+10
-10
doc/src/sgml/history.sgml
doc/src/sgml/history.sgml
+1
-1
doc/src/sgml/release.sgml
doc/src/sgml/release.sgml
+4
-4
doc/src/sgml/typeconv.sgml
doc/src/sgml/typeconv.sgml
+5
-5
未找到文件。
doc/src/sgml/history.sgml
浏览文件 @
8fc97e82
...
...
@@ -227,7 +227,7 @@
<listitem>
<para>
Additional <acronym>SQL92</acronym>-compliant language features have been added,
including primary keys, quoted identifiers, literal string type coer
sion,
including primary keys, quoted identifiers, literal string type coer
cion,
type casting, and binary and hexadecimal integer input.
</para>
</listitem>
...
...
doc/src/sgml/release.sgml
浏览文件 @
8fc97e82
...
...
@@ -414,7 +414,7 @@ Fix bug in pg_dump -z
Memory overrun cleanups(Tatsuo)
Fix for lo_import crash(Tatsuo)
Adjust handling of data type names to suppress double quotes(Thomas)
Use type coer
s
ion for matching columns and DEFAULT(Thomas)
Use type coer
c
ion for matching columns and DEFAULT(Thomas)
Fix deadlock so it only checks once after one second of sleep(Bruce)
Fixes for aggregates and PL/pgsql(Hiroshi)
Fix for subquery crash(Vadim)
...
...
@@ -475,7 +475,7 @@ EXPLAIN all indices used(Tom)
Implement CASE, COALESCE, NULLIF expression(Thomas)
New pg_dump table output format(Constantin)
Add string min()/max() functions(Thomas)
Extend new type coer
s
ion techniques to aggregates(Thomas)
Extend new type coer
c
ion techniques to aggregates(Thomas)
New moddatetime contrib(Terry)
Update to pgaccess 0.96(Constantin)
Add routines for single-byte "char" type(Thomas)
...
...
@@ -672,7 +672,7 @@ Fix for lo_import() crash(Bruce)
Better search for install program(Tom)
Timezone fixes(Tom)
HPUX fixes(Tom)
Use implicit type coer
s
ion for matching DEFAULT values(Thomas)
Use implicit type coer
c
ion for matching DEFAULT values(Thomas)
Add routines to help with single-byte (internal) character type(Thomas)
Compilation of libpq for Win32 fixes(Magnus)
Upgrade to PyGreSQL 2.2(D'Arcy)
...
...
@@ -734,7 +734,7 @@ asynchronous messages and interrupts thanks to Tom Lane.
<listitem>
<para>
The parser will now perform automatic type coer
s
ion to match arguments
The parser will now perform automatic type coer
c
ion to match arguments
to available operators and functions, and to match columns and expressions
with target columns. This uses a generic mechanism which supports
the type extensibility features of <productname>Postgres</productname>.
...
...
doc/src/sgml/typeconv.sgml
浏览文件 @
8fc97e82
...
...
@@ -14,7 +14,7 @@ to understand the details of the type conversion mechanism.
However, the implicit conversions done by <productname>Postgres</productname>
can affect the apparent results of a query, and these results
can be tailored by a user or programmer
using <emphasis>explicit</emphasis> type coer
s
ion.
using <emphasis>explicit</emphasis> type coer
c
ion.
</para>
<para>
...
...
@@ -26,7 +26,7 @@ for more information on specific data types and allowed functions and operators.
<para>
The Programmer's Guide has more details on the exact algorithms used for
implicit type conversion and coer
s
ion.
implicit type conversion and coer
c
ion.
</para>
<sect1>
...
...
@@ -163,14 +163,14 @@ All type conversion rules are designed with several principles in mind:
<itemizedlist mark="bullet" spacing="compact">
<listitem>
<para>
Implicit conversions should never have suprising or unpredictable outcomes.
Implicit conversions should never have su
r
prising or unpredictable outcomes.
</para>
</listitem>
<listitem>
<para>
User-defined types, of which the parser has no apriori knowledge, should be
"higher" in the type h
ei
rarchy. In mixed-type expressions, native types shall always
User-defined types, of which the parser has no a
-
priori knowledge, should be
"higher" in the type h
ie
rarchy. In mixed-type expressions, native types shall always
be converted to a user-defined type (of course, only if conversion is necessary).
</para>
</listitem>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录