6月以來全球股市疲弱，但是台股月跌幅達4.6%，遠高於美股的2.4%及韓股的2.2%。觀察個股動態，智慧手機品牌廠宏達電（2498）5月領先大盤反轉，6月跌幅更高達20.8%；
反觀手機代工的華寶（8078），5、6月股價漲幅分別達15.2%及27.4%，形成強烈對比。
事實上，宏達電今年EPS（Earnings Per Share，每股純益）有80元實力，但股價高處不勝寒，大金主外資連2月累計賣超2萬3526張！
華寶自24元低價反攻，憑著中低階智慧手機搶市的想像空間，被高盛列入強烈買進名單。事實上，為諾基亞（NOKIA）代工的微軟新機，要到第4季才會放量出貨，今年EPS預估僅0.5元，卻有外資和投信買盤積極擁護，高、低價股果真是命運大不同！
這是朋友轉寄給我的，在經歷過塑化劑事件之後，每天開始對吃的喝的東西都會特別留意。
開始減少購買某些大企業的不負責任食品
(因為覺得只顧著賺錢，不顧消費者健康的企業，不值得繼續購買他們的產品)
而義美是這次風暴中，我認為真的有良心的企業
(原來還是有些企業是用良心在做事業)
這個偏方滿好用的，是朋友寄給我的，就順便貼上來..!!
今天下午去幫兒子買一雙鞋子，老闆看了兒子的腳說：「怎這麼多紅豆冰呀！」
我很無奈地回答：「蚊子真的好多哦！市面上賣的防蚊液每家都說很天然，但裡頭還是摻了，一些化學成份。
雖然我有買了一瓶但最後還是沒在用」。
http://www.kui.name/blog/2011/mongodb-%E6%96%87%E6%AA%94%E9%96%B1%E8%AE%80%E7%AD%86%E8%A8%98.html
NoSQL 資料庫在上年炒得很熱，於是我也萌生了使用 NoSQL 資料庫寫一個應用的想法。首先來認識一下 NoSQL。NoSQL 是一個縮寫，含義從最初的 No-SQL 到現在已經成為了 Not-Only-SQL。確實後面一種解釋比較符合 NoSQL 的使用場景。
現在網路上被人所知的 NoSQL 資料庫可以在這個網頁（http://nosql-database.org）看到。這個列表林林總總一大堆，要選擇哪個資料庫入手呢？
http://www.arthurtoday.com/2011/02/windows-mongodb.html
雖然阿舍之前玩的 Domino/Notes 也算是 NoSQL，不過，阿舍最近想玩玩別的 NoSQL 的資料庫，，於是就是就去找了一下，最後剩下 MongoDB 和 CouchDB 二個來選，經過一番比較後，阿舍決定選擇 MongoDB 來用，原因是覺得 MongoDB 的功能比較多，而且，文件比較齊全，所以，阿舍就選了 MongoDB。
不過，阿舍一開始有點誤會 MongoDB 了，一直以為它是 Embeded Database，其實，MongoDB 是一套完整的資料庫系統，需要有 Server 端的，是要先啟動伺服器才可以連線的啊 !
MongoDB 在 Windows 的安裝方式很簡單，只要到這裡點選 Windows 版本的程式，然後，把它解壓縮後，然後，把解壓縮出來的資料夾更名成 mongodb，再來，把這個資料夾移到 c:\ 下，變成 c:\mangodb 就算完成安裝一半了。
接著，是要幫 MongoDB 建立放資料庫的地方，預設是在 c:\data\db 這裡，所以，請在 C 槽建立這個資料夾，這樣就算完成了哩 !
果然還是”天然的最好”
請自己看看你每天吃進了多少有毒物!
整理一下毒起雲劑的下游廠商
資料來源是衛生署
http://www.mongodb.org/display/DOCS/CSharp+Driver+Tutorial
CSharp Driver Tutorial
C# Driver version v1.0
This tutorial is for v1.0 of the C# Driver.
Introduction
http://www.mongodb.org/display/DOCS/SQL+to+Mongo+Mapping+Chart
MySQL executable Oracle executable Mongo executable
mysqld
oracle
mongod
MongoDB 官方網站
http://www.mongodb.org/
下載
http://www.mongodb.org/downloads
安裝教學
http://msdn.microsoft.com/zh-tw/magazine/ff798277.aspx
Last time, I continued my exploration of MongoDB via the use of exploration tests. I described how to start and stop the server during a test, then showed how to capture cross-document references and discussed some of the reasoning behind the awkwardness of doing so. Now it’s time to explore some more intermediate MongoDB capabilities: predicate queries, aggregate functions and the LINQ support provided by the MongoDB.Linq assembly. I’ll also provide some notes about hosting MongoDB in a production environment.
When We Last Left Our Hero . . .
For reasons of space, I won’t review much of the previous articles; instead, you can read them online in the May and June issues at msdn.microsoft.com/magazine. In the associated code bundle, however, the exploration tests have been fleshed out to include a pre-existing sample set of data to work with, using characters from one of my favorite TV shows. Figure 1 shows a previous exploration test, by way of refresher. So far, so good.
In my previous article, MongoDB’s basics took front and center: getting it installed, running and inserting and finding data. However, I covered only the basics—the data objects used were simple name/value pairs. That made sense, because MongoDB’s “sweet spot” includes unstructured and relatively simple data structures. But surely this database can store more than just simple name/value pairs.
In this article, we’ll use a slightly different method to investigate MongoDB (or any technology). The procedure, called an exploration test, will help us find a possible bug in the server and, along the way, highlight one of the common issues object-oriented developers will run into when using MongoDB.
In Our Last Episode …
First we’ll make sure we’re all on the same page, and we’ll also cover some slightly new ground. Let’s look at MongoDB in a bit more structured fashion than we did in the previous article (msdn.microsoft.com/magazine/ee310029). Rather than just create a simple application and hack on it, let’s kill two birds with one stone and create exploration tests—code segments that look like unit tests but that explore functionality rather than try to verify it.
http://msdn.microsoft.com/zh-tw/magazine/ee310029.aspx
Over the past decade or so, since the announcement of the Microsoft .NET Framework in 2000 and its first release in 2002, .NET developers have struggled to keep up with all the new things Microsoft has thrown at them. And as if that wasn’t enough, “the community”—meaning both developers who use .NET on a daily basis and those who don’t—has gone off and created a few more things to fill in holes that Microsoft doesn’t cover—or just to create chaos and confusion (you pick).
One of those “new” things to emerge from the community from outside of the Microsoft aegis is the NoSQL movement, a group of developers who openly challenge the idea that all data is/will/must be stored in a relational database system of some form. Tables, rows, columns, primary keys, foreign key constraints, and arguments over nulls and whether a primary key should be a natural or unnatural one … is nothing sacred?
