DB2 Viper 2 beta - 兼容性功能需要反馈 [英] DB2 Viper 2 beta - compatibility features Feedback needed
问题描述
嗨大家好，
我的队友们有一些额外的时间在他们的手上所以我们决定用b
$兼容性功能。
我们不介意帮助验证语义匹配....
所以对于那些有幸或被诅咒有竞争力的DBMS的人来说，这是一个
我们添加的内容列表：
1. ** DUAL
始终无需为模式添加前缀
2. ** ROWNUM
3. **（+）外连接语法
4.最低/最高/ NVL / DECODE
5. TO_DATE / TO_CHAR改进
DB2支持最常见的模式，除了那些需要语言的模式
意识
6. ** CONNECT BY
这是一个功能下降，性能下降将跟随
7.一大堆语法糖如：
Seq.NEXTVAL和seq.CURRVAL表示法
UNIQUE而不是DISTINCT
MINUS而不是EXCEPT
未命名的嵌套子查询（又名内联）观看次数）
" SELECT * FROM（SELECT * FROM T）"
CROSSJOIN
8. BITAND / BITOR / .... 。
标有**的功能需要注册表设置：
db2set DB2_COMPATIBILITY_VECTOR = 3F
应该打开所有内容。
移植应用程序还有其他功能：
GLOBAL VARIABLES
新的ARRAY数据类型
一个新的RID（）函数可用于映射ROWID
文档： https://publib.boulder.ibm.com/infoc...v9r5/index.jsp
享受
Serge
-
Serge Rielau
DB2解决方案开发
IBM多伦多实验室
-
Serge Rielau
DB2解决方案开发
IBM多伦多实验室
Hi folks,
My fellow team mates had some extra time on their hands so we decided to
spice up DB2 with a grab-bag of compatibility features.
We wouldn''t mind help validating the semantics match....
So for those of you blessed or cursed with a competitive DBMS here is a
list of what we''ve added:
1. ** DUAL
Always works without prefixing a schema
2. ** ROWNUM
3. ** (+) outer join syntax
4. LEAST/GREATEST/NVL/DECODE
5. TO_DATE/TO_CHAR improvement
DB2 supports most common patterns except those requiring language
awareness
6. ** CONNECT BY
This is a function drop, performance drop will follow
7. A slew of syntactic sugar like:
Seq.NEXTVAL and seq.CURRVAL notation
UNIQUE instead of DISTINCT
MINUS instead of EXCEPT
Unnamed nested subqueries (aka inline views)
"SELECT * FROM (SELECT * FROM T)"
CROSSJOIN
8. BITAND/BITOR/.....
The features marked with ** require a registry setting:
db2set DB2_COMPATIBILITY_VECTOR=3F
should switch everything on.
There are other features those porting apps will value:
GLOBAL VARIABLES
A new ARRAY data type
A new RID() function can be used to map ROWID
Docs: https://publib.boulder.ibm.com/infoc...v9r5/index.jsp
Enjoy
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
推荐答案
Serge Rielau写道：
[...]
Serge Rielau wrote:
[...]
CROSSJOIN
CROSSJOIN
任何机会NATURAL JOIN将在附近实施未来？
/ Lennart
[...]
Any chance NATURAL JOIN will be implemented in a near future?
/Lennart
[...]
Lennart写道：
Lennart wrote:
Serge Rielau写道：
[...]
Serge Rielau wrote:
[...]
> CROSSJOIN
> CROSSJOIN
任何机会在不久的将来实施NATURAL JOIN？
Any chance NATURAL JOIN will be implemented in a near future?
我玩弄了它。但是原型花了一天多的时间，
所以我保释;-)
如果我们发现NATURAL JOIN变得流行那么很有可能。
不一定是按照名称排列列的工程专长... ;-)
到目前为止，我还没有在现场看到它。 />
干杯
Serge
-
Serge Rielau
DB2解决方案开发
IBM多伦多实验室
I toyed with it. But it took more than a day to prototype,
so I bailed ;-)
If we find that NATURAL JOIN becomes popular then it is quite possible.
Not exactly an engineering feat to line up columns by name... ;-)
So far I haven''t seen it in the field much though.
Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Serge Rielau写道：
Serge Rielau wrote:
Lennart写道：
Lennart wrote:
> Serge Rielau写道：
[...]
>Serge Rielau wrote:
[...]
>> ; CROSSJOIN
>> CROSSJOIN
任何机会在不久的将来实施NATURAL JOIN？
Any chance NATURAL JOIN will be implemented in a near future?
我玩弄了它。但是原型花了一天多的时间，
所以我保释;-)
如果我们发现NATURAL JOIN变得流行那么很有可能。
不一定是按名称排列列的工程专长...... ;-)
I toyed with it. But it took more than a day to prototype,
so I bailed ;-)
If we find that NATURAL JOIN becomes popular then it is quite possible.
Not exactly an engineering feat to line up columns by name... ;-)
告诉我在哪里投票:-)。说真的，虽然这会拯救我（而且我会猜测其他人）大量的打字。作为奖励，sql将会变得不那么明显的混乱。作为一个例子我更喜欢：
选择...来自NYA.COURSE_OFFERING co NATURAL JOIN
NYA.PICKED_COURSE_OFFERING pco where ...
结束：
选择...来自NYA.COURSE_OFFERING co INNER JOIN
NYA.PICKED_COURSE_OFFERING pco ON
（co.ADMISSIONROUND_ID，co.EDUCATIONORG_ID，co.COURSE OFFERING_ID）=
（pco.ADMISSIONROUND_ID，pco.EDUCATIONORG_ID，pco.COU RSEOFFERING_ID）
其中...
无论如何，感谢有关测试版的信息。如果我得到时间，我会
可能参加。
Just tell me where to vote :-). Seriously though it would save me (and I
guess others) a tremendous amount of typing. As a bonus the sql will
become less cluttered with the obvious. As an example I would prefer:
select ... from NYA.COURSE_OFFERING co NATURAL JOIN
NYA.PICKED_COURSE_OFFERING pco where ...
over:
select ... from NYA.COURSE_OFFERING co INNER JOIN
NYA.PICKED_COURSE_OFFERING pco ON
(co.ADMISSIONROUND_ID,co.EDUCATIONORG_ID,co.COURSE OFFERING_ID) =
(pco.ADMISSIONROUND_ID,pco.EDUCATIONORG_ID,pco.COU RSEOFFERING_ID)
where ...
Anyhow, thanks for the info regarding the beta. If I get the time I''ll
probably participate.
到目前为止，我还没有看到它尽管如此。
干杯
Serge
So far I haven''t seen it in the field much though.
Cheers
Serge
这篇关于DB2 Viper 2 beta - 兼容性功能需要反馈的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
