2008-04-18 Fri
MySQL has a lot of string data types - CHAR, VARCHAR, BLOB, TEXT, ENUM and bunch of variants such as VARBINARY but I think it is not enough
I would also like to see type HEXCHAR which would be able to store hex strings, such as those returned as MD5() and SHA1() efficiently. With little modification it could work for UUID() as well (it adds some dashes). Currently it is quite inconvenient to deal with strings like that in MySQL. Either you store them as strings and waste space or you spend them as binary and deal with inconvenience of having not readable strings in the table OR adding UNHEX() everywhere - which also adds overhead.
Another one I would like to see is zBLOB or zTEXT (or call them BLOB COMPRESSED/ TEXT COMPRESSED) which would transparently compress the blobs when they are inserted and retrieved from the database - this would allow to avoid having COMPRESS()/UNCOMPRESS() everywhere which clobbers things or compressing/uncompressing on the client.
It would be best if last one is optimized so if BLOB is not used in any WHERE clause (HAVING, GROUP BY etc) you could actually transparently decompress it on the client and compress bad. Though this is likely to require more significant changes in MySQL so I would not expect to happen quickly. The basic support should not be that hard though.
Entry posted by peter | 2 comments
I presented 3 sessions between IOUG and OAUG, which were all well attended with over 150 people per session. I guess security is really starting to become ingrained at many organizations. I was somewhat surprised at the number of organizations relatively current with CPU patches based on the informal and highly unscientific "show of hands" surveys.
The PowerPoint presentations from my 3 sessions can be downloaded here -
Oracle Applications Users Group (OAUG)
Oracle E-Business Suite Critical Patch Updates: Insight and Understanding
Independent Oracle Users Group (IOUG)
Oracle Database Critical Patch Updates: Unwrapped
Real-life Database Security Mistakes
Welcome to the 93th edition of Log Buffer, the weekly review of database blogs.
Conference season is upon us, so it’s been a busy week. There was the MySQL Conference & Expo, so let’s look at that.
Arjen Lentz posts about Sunday’s community dinner, including the arrival of an unexpected guest. Two photos: one of Pythian’s Paul Vallée getting some Sun; the second from the pre-conference dinner.
Zack Urlocker has a couple pieces with both photos and links to video of the keynote addresses from Marten Mickos, Jonathan Schwartz, and Rich Green. From Wednesday, and from Thursday.
Congratulations are due to Baron Schwartz, Diego Medina, and Sheeri Cabral. Baron reports from the conference that the three of them were awarded the 2008 MySQL Community Awards, and his piece makes for a very apt acceptance speech. Here’s Kaj Arnö’s more official post on the Community Awards.
Baron also has good summaries of the conference course: day one, and day two.
Elsewhere on the MySQL scene, much ado about the immediate roadmap for the DBMS, as introduced at the conference. Jeremy Cole got things going, writing, MySQL to launch new features only in MySQL Enterprise: “MySQL will start offering some features . . . only in MySQL Enterprise. This represents a substantive change to their development model — previously they have been developing features in both MySQL Community and MySQL Enterprise. However, with a shift to offering some features only in MySQL Enterprise, this means a shift to development of those features occurring . . . only in MySQL Enterprise.” This post got a lot of comments, including from MySQL boss Marten Mickos.
Shadowman on your shoulder?
Fedora on your forearm?
Tux on your tush?
We’re looking for people with Red Hat, Fedora, Creative Commons, and other awesome open source and related tattoos to feature in the magazine.
Even better, have you been thinking about getting some new geek ink but haven’t yet? Have a friend videotape it and send us the footage.
If you’re interested in showing off your ink, drop us a line.
Thanks!
Author:NinGoo posted on NinGoo.net
毫无疑问,开源运动最初更多的是一种精神运动,虽然最终不可避免的被商业化。Sun显然没有真正的理解开源,甚至没能合格的利用开源。虽然Sun一直在抱怨说向开源社区贡献了最多的源代码却没有得到应用的尊重,虽然已经将压箱底的Java和Solaris都整成了OpenJava和OpenSolaris,但看起来这更多的是被逼无奈,而不是真心的拥抱开源。
现在Sun说要对MySQL选择性开源,一些企业级新特性的源代码将不再开放,患得患失的小家子气一下表露无遗。保留的这些代码未必能吸引更多的客户,却让原本对于Sun收购MySQL持观望态度的开源人士找到了攻击和离开的借口,如此费力不讨好的事情,Sun居然能堂而皇之的在The 2008 MySQL Conference & Expo期间干出来,真是脑子进水了。
开源是一种精神,半推半就是不能赢得人心的。
Related Articles
Author:NinGoo posted on NinGoo.net
家里的台式机上装了个alexa工具条,今天偶然发现blog的排名出现了大幅度的上升,于是进去看了下,发现alexa的排名算法做了比较大的修改。原来alexa的排名的主要数据来源是alexa工具条,这个东西,除了一些个人站长或者专门帮别人刷排名的,估计安装的不多,所以得到的数据的准确度是值得怀疑的。想想以前国内多少网站靠着这个排名作为拉到风险投资的救命稻草,原来不过是建在沙滩上的城堡而已。每一次alexa排名算法的变化,都是有人欢喜有人叫,呵呵。
现在还拿alexa说事的应该不多了,web2.0们都喜欢说自己有多少注册用户有多少用户生成的内容了,没了关注度的alexa做出了最大的一个改变,不再过于依赖工具条的数据了。从一开始知道alexa,就对他们依赖工具条的数据来做排名就觉得很疑惑,他们居然说In recent months才收到用户的抱怨,借口而已吧,真正的原因,是一直无法获得足够的数据呢?还是一直写不出算法?
When Alexa began displaying rankings in 1998 it was with the goal of showing Alexa Toolbar users how popular any given site was within the Alexa community. We generated the rankings through an analysis of Internet usage by people who use the Alexa Toolbar. Since that time we’ve been delighted to see that the Alexa Rankings have become a yardstick by which website popularity is measured. We are grateful to the thousands of people who come to Alexa.com each day to check the Alexa Rankings.
In recent months we’ve heard from our Alexa users that understanding Internet usage beyond Alexa Toolbar users was increasingly of interest. Ask and you shall receive!
We listened to your suggestions, and we believe that our new rankings system is much closer to what you asked for. We now aggregate data from multiple sources to give you a better indication of website popularity among the entire population of Internet users.
Related Articles
接到同事的电话,某省的一个用于监控的siteview数据库启动不了了,登录后检查alertlog发现:
9868 redo blocks read, 655 data blocks need recovery
Thu Apr 19 16:52:42 2007
Started recovery at
Thread 1: logseq 700, block 194931, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 3 Seq 700 Reading mem 0
Mem# 0 errs 0: C:\ORACLE\ORADATA\IMALLSV\REDO03.LOG
Thu Apr 19 16:52:43 2007
Ended recovery at
Thread 1: logseq 700, block 204799, scn 0.147914177
655 data blocks read, 655 data blocks written, 9868 redo blocks read
Crash recovery completed successfully
Thu Apr 19 16:52:43 2007
Errors in file c:\oracle\admin\imallsv\bdump\imallsv_lgwr_4180.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\IMALLSV\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: 无法打开文件
O/S-Error: (OS 2) 系统找不到指定的文件。
Thu Apr 19 16:52:43 2007
Errors in file c:\oracle\admin\imallsv\bdump\imallsv_lgwr_4180.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\IMALLSV\REDO01.LOG'
ORA-27041: unable to open file
OSD-04002: 无法打开文件
O/S-Error: (OS 2) 系统找不到指定的文件。
ORA-313 signalled during: alter database open...
原来是redolog被干掉了,其实对于redolog的丢失,如果丢失的不是active或者current(这个在win中一般不会被删除,因为使用时被锁定),我们可以用以下的方式恢复:
SQL*Plus: Release 9.2.0.1.0 - Production on 星期四 4月 19 17:05:03 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
连接到:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> shutdown immediate
ORA-01109: 数据库未打开
已经卸载数据库。
ORACLE 例程已经关闭。
SQL> startup mount;
ORACLE 例程已经启动。
Total System Global Area 487660924 bytes
Fixed Size 454012 bytes
Variable Size 209715200 bytes
Database Buffers 276824064 bytes
Redo Buffers 667648 bytes
数据库装载完毕。
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
---------- ---------- ---------- ---------- ---------- --- ----------------
FIRST_CHANGE# FIRST_TIME
------------- ----------
1 1 699 104857600 1 NO INACTIVE
147462354 17-4月 -07
2 1 0 104857600 1 NO UNUSED
0 16-4月 -07
3 1 700 104857600 1 NO INVALIDATED
147678398 17-4月 -07
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR 位于第 1 行:
ORA-01139: RESETLOGS 选项仅在不完全数据库恢复后有效
SQL> recover database until cancel;
完成介质恢复。
SQL> alter database open resetlogs;
数据库已更改。
SQL>
SQL> shutdown immediate;
数据库已经关闭。
已经卸载数据库。
ORACLE 例程已经关闭。
SQL> startup
ORACLE 例程已经启动。
Total System Global Area 487660924 bytes
Fixed Size 454012 bytes
Variable Size 209715200 bytes
Database Buffers 276824064 bytes
Redo Buffers 667648 bytes
数据库装载完毕。
数据库已经打开。
至此,恢复完成。^_^
2008-04-17 Thu
2008-04-16 Wed
2008-04-15 Tue
AnySQL.net
DBA notes
Oracle & Starcraft
eagle's home
Give you some color to see see!
AnySQL.net English
Oracle Scratchpad
Oracle Life
OracleDBA Blog---请享受无法回避的痛苦!
Uploads from dbanotes
Chanel [K]
xzh2000的博客
Oracle Security Blog
ERN空间
Eddie Awad's Blog
MySQL Performance Blog
The Tom Kyte Blog
del.icio.us/fenng/oracle
AIXpert
O'Reilly Databases
Red Hat Magazine
DBASupport
DB2 Magazine 中文版
developerWorks : AIX 专区的文章,教程
Pythian Group Blog » Log Buffer
车东[Blog^2]
blue_prince
玉面飞龙的BLOG
此生 今世
人生就是如此
Orange Tiger 木匠 的 移民生活
生活帮-LifeBang
Hey!! Sky!
dba on unix
Oracle Notes Wiki
Brotherxiao's Home
柔嘉维则@life.oracle.eng
Fenng's shared items in Google Reader
jametong's shared items in Google Reader
缥缈游侠-logzgh
Tanel Poder's blog: Core IT for geeks and pros
DBA Tools
ilonng
yangtingkun
NinGoo@Net
Oracle & Unix
Inside the Oracle Optimizer - Removing the black magic
Ricky's Test Blog
DBA@Taobao
存储部落
Think in 88
Alibaba DBA Team
Oracle Team @SNC
淘宝数据仓库团队
OracleBlog.cn




