今天上中行的网站，本来是找信息的，却发现了很多大问题，比如：
- DNS 只解析 www.boc.cn，不解析 boc.cn
- 供下载的申请表竟然用 rar 打包，是不是在考验申请人的计算机操作能力？
- 网银操作依赖于 IE
- 安全增强依赖于 ActiveX
- SSL 证书只是基本型的，而不是银行业界普及的增强型
- 网页用 gb2312 编码，而非最适合国际公司的 utf-8
- 网页申明为 xhtml，但显然不知 xhtml 为何物
- table 布局
小问题肯定数都数不过来，我也没心情帮他们去纠错。
Day: June 16, 2010
-
Problemic boc.cn
-
1and1 waste me two days
订了一个 1&1 Cloud Server，两天了还没法用。在 1&1 control panel 里一点那个 cloud server，就抛给我一个 500 Internal Server Error。这是在 1＆1 control panel 里的错误，不是我订的 cloud server 上的错误。
一开始我还以为下订单时某个环节没做到，我拼命发 email，拼命打电话（电话很长时间才有人接，接了也会被掐，还是email support 好一些），辗转了 N 个来回以后被告知，1&1 的程序有个错误，让我耐心等。晕啊，浪费我两天时间。
-
What if I change the EAV attribute backend type in Magento?
The question is raised because in my catalog_category, I have a user attribute originally 255 length varchar. Now I am told by users it was not long enough for block text. I want to change it to text type in mysql to solve the problem.
I know EAV attributes use different tables for different type. My worry is moving attribute value from varchar table to text table when changing the EAV attribute backend type. Anyway, I have to try before I know. Here is my steps:
- go to table magento_eav_attribute, find the attribute, change backend_type from varchar to text
- (what’s next?) I am about to change something else, but surprisingly, nothing else! All done after step 1.
I do not need to move old values from magento_catalog_category_entity_varchar to magento_catalog_category_entity_text. After change attribute’s backend_type, Magento can still read existing value from magento_catalog_category_entity_varchar, but if I save the category, the value will save to magento_catalog_category_entity_text. Old value is not deleted from magento_catalog_category_entity_varchar, but it does no harm.
I am curious at how Magento did it – Does Magento go through 5 tables (datetime, decimal, int, text, varchar) to get a value? Or Magento cache attributes’ backend type (so even I make changes in magento_eav_attribute, Magento still have records of old type)?