2008-04-19 Sat
- 不要设置自动回复!自动回复一点意义也没有,徒增对方的负担。而且,我恨死自动回复了,某一段时间邮箱几乎要被自动回复塞爆,只要挨个回复请发件人关掉。
- 一定要写主题。如果不清楚你的邮件主要想说什么,还是干脆不要写邮件的好。不写主题会增加被判定为垃圾邮件的可能性。
- 署名。如果和收件人没有熟到一看email地址就知道是谁,还是署个名吧。另外,配置邮箱的时候,姓名一栏也应该填点有语义的内容。
- 不要用花里胡哨的信纸。信纸什么的非常影响阅读,换了不同的邮件阅读器会发现内文变得一团糟。童心未泯者无视好了。
- 没事干别胡乱转发无聊的邮件。这种邮件在转发后暴露了很多无辜者的邮件地址,很讨厌。这种行为很招垃圾邮件的。
- 用密件抄送转发。不要轻易泄露不相关人的邮件地址,想想看垃圾邮件都是怎么来的。
写在这里,备用。
San Francisco-based blogging startup Six Apart has made a significant acquisition, we heard today from someone with knowledge of the deal. “Significant” in the sense of a possible strategic shift for the company, if not in terms of deal size. It will be announced in the next few days.
Who did they acquire? Put your best guess in the comments. First comment that is correct gets a 2 GB iPod shuffle with “I Love TechCrunch” engraved on the back.
Crunch Network: CrunchBoard because it’s time for you to find a new Job2.0
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 | 6 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
2008-04-17 Thu
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




