跟着¾|‘上‹¹è¡Œçš„学生选课表的例子复习了一下： http://www.cnblogs.com/buzaixian/archive/2009/09/21/1571365.html
˜q™ç¯‡æ–‡å­—在网上被转蝲烂了åQŒé‡Œé¢æœ‰äº›sql适合用在应用¾pȝ»Ÿé‡Œï¼Œæœ‰äº›â€œæŠ¥è¡¨â€çš„æ„?觉更重些åQŒä¸»è¦æ˜¯æƒ›_¤ä¹ å‰è€…。前20条大体还挺好åQŒåŽ30条明昑ցæŠ¥è¡¨é£Žæ ¼äº†ï¼Œè€?且后面选例良莠不齐åQŒé€‰äº†12个例子做¾lƒä¹ åQŒï¼ˆå…¶å®žå¾ˆå¤šè¯­æ³•åQŒcase, any/all, union之类的都没包括）åQŒç”¨mysql数据库，òq¶å…±äº«è‡ªå·±é€ å‡ºæ¥çš„数据。关于这12æ?sql, 修正了原文中有纰漏的地方ã€?
sql是基本技能，若能写得好也挺精彩的åQŒè¿˜åœ¨ç‘ô¾l­ç»ƒä¹ ã€‚绝不提倡努力写复杂sql 解决业务问题。应用系¾lŸé‡Œå¦‚果存在很复杂的sqlåQŒå¾€å¾€æ­ç¤ºäº†ä¸šåŠ¡é€»è¾‘向下泄露 到sql层的问题åQŒä¸åˆ©äºŽ¾l´æŠ¤å’Œæ‰©å±•ï¼Œè™½ç„¶˜q™æ ·¼‹®å®žå¸¸èƒ½æé«˜˜qè¡Œæ•ˆçŽ‡ã€‚具体情å†?自行取舍ã€?
下面的例子都是比较通用的sql, 其实针对特定的数据库åQŒéœ€è¦å­¦çš„也挺多åQŒæ¯”å¦?oracle dbçš„decode函数, rowid, rownum, connect by 虽然不通用åQŒä½†æ˜¯å¾ˆå®žç”¨ã€?

数据可以在这里下载，只是用作¾lƒä¹ åQŒæ²¡åšä“Q何外键关联：http://115.com/file/an2svxbe#sql-study.sql

整理的sql在下面：
Student(S#,Sname,Sage,Ssex) 学生�
Course(C#,Cname,T#) 评¡¨‹è¡?
SC(S#,C#,score) 成ç‡Wè¡?
Teacher(T#,Tname) 教师�
1. 选出每门功课都及格的学号
select distinct `s#` from sc where `s#` not in (select `s#` from sc where score <60)
2. 查询â€?”课½E‹æ¯”â€?”课½E‹æˆ¾l©é«˜çš„所有学生的学号åQ?
SELECT c01.`s#` from (select `s#`, `score` from sc where `c#`=1) c01,
                          (select `s#`, `score` from sc where `c#`=2) c02
                     where c01.`s#` = c02.`s#` and c01.score > c02.score
3.  查询òq›_‡æˆç‡W大于60分的同学的学号和òq›_‡æˆç‡WåQ?
select `s#`, avg(score) from sc group by `s#` having avg(score) > 60
4. 查询所有同学的学号、姓名、选课数、æ€ÀLˆ¾l©ï¼›
select student.`s#`, student.`Sname`, count(`c#`), sum(score) from student left outer join sc on student.`s#` = sc.`s#` group by student.`s#`, sc.`s#`
5.查询没学˜q‡â€œå¶òq³â€è€å¸ˆè¯„¡š„同学的学受÷€å§“名；
select student.`s#`, student.`Sname` from student where student.`s#` not in (select distinct(sc.`s#`) from teacher, course, sc where Tname='叶åã^' and teacher.`t#` = course.`t#` and sc.`c#`= course.`c#` )
6. 查询学过â€?01”åƈ且也学过¾~–号â€?02”课½E‹çš„同学的学受÷€å§“å?
select student.`s#`, student.sname from student, sc where student.`s#` = sc.`s#` and sc.`c#` = 1 and exists (select * from sc sc_2 where sc_2.`c#`=2 and sc.`s#`=sc_2.`s#`)
7. 查询学过“叶òq³â€è€å¸ˆæ‰€æ•™çš„所有课的同学的学号、姓å?(巧妙)
select `s#`, sname from student where `s#` in
       (select `s#` from sc, teacher, course where tname='叶åã^' and teacher.`t#`=course.`t#` and course.`c#`= sc.`c#` group by `s#` having count(sc.`c#`)=
               (select count(`c#`) from teacher, course where tname='å?òq? and teacher.`t#`=course.`t#`) )
8. 查询评¡¨‹¾~–号â€?02”的成ç‡W比课½E‹ç¼–号â€?01”课½E‹ä½Žçš„所有同学的学号、姓å?(有代表æ€?
select `s#`, sname from (select student.`s#`, student.sname, score, (select score from sc sc_2 where student.`s#`=sc_2.`s#` and sc_2.`c#`=2) score2 from student , sc where
       sc.`s#`=student.`s#` and sc.`c#`=1) s_2 where score2 < score
9.查询没有学全所有课的同学的学号、姓�
select student.`S#`, Sname from student, sc where student.`s#` = sc.`s#` group by `s#`, sname having count(`c#`) < (select count(`c#`) from course)
10. 查询臛_°‘有一门课与学号äØ“â€?02”的同学所学相同的同学的学号和姓名åQ?
select distinct(sc.`s#`), sname from student, sc where student.`s#`=sc.`s#` and `c#` in (select `c#` from sc where `s#`=002)
11. 把“SC”表中“叶òq³â€è€å¸ˆæ•™çš„评¡š„成ç‡W都更改äؓ此课½E‹çš„òq›_‡æˆç‡WåQ?
update sc inner join
       (select sc2.`c#`, avg(sc2.score) score from sc sc2, teacher, course where
              sc2.`c#`=course.`c#` and tname='叶åã^' and teacher.`t#` = course.`t#` and course.`c#`=sc2.`c#` group by course.`c#`) sc3 on sc.`c#`=sc3.`c#` set sc.score=sc3.score
12. 查询2åïLš„同学学习的课½E‹ä»–都学了的同学的学åøP¼›åQˆæ³¨æ„ç†è§£ï¼šwhere语句çš?½W¬ä¸€ä¸ªæ¡ä»¶è¿‡æ»¤æŽ‰ä¸æ»¡­‘³c#的记录，再group byåQŒå°±æ¯”较清晰åQ?
select `S#` from SC where `C#` in (select `C#` from SC where `S#`=2)
    group by `S#` having count(*)=(select count(*) from SC where `S#`=2);

æ™ø™”招聘的原链接åQ?http://jobs.zhaopin.com/P2/CC0003/1191/J902/509/CC000311917J90250983000.htm?f=ss

软äšg分析师A

Job Responsibilities:

The mission of this role is to improve the customer competence of SAS. You are expected and will be cultivated to be an expert who understands SAS technology/solution, globalization and the domain knowledge. In more details, duties will include:Conducts customer experience testing and best practice testing for SAS technologies and solutions;

• Provides counseling on localized SAS software;
• Provides internal SAS practice training and implementation guidance, especially for new product and solutions;
• Collects the feedback from customers.

Qualifications:

• Hands on experience in business intelligence;
• Passion on programming, hands on Java programming or C/C++ experiences and skills;
• Better skills on communication, customer-facing and problem-resolving;
• The ability to work as member of a team, virtual team and individual;
• Good written and spoken English;
• Master’s or Bachelor's degree.

Preferences:

• SAS products and technology knowledge;
• Domain Knowledge in retail industry, financial management, risk management, CRM, etc.;
• Experience in internationalization and localization.

发送简历至:bjrnd@sas.com

[fangang]我们评ä­h高质量代码有三要素：可读性、可¾l´æŠ¤æ€§ã€å¯å˜æ›´æ€§ã€?/p>

[vcycyv]同意˜q™ä¸‰ä¸ªæ–¹é¢ã€‚我总这æ ähƒ³åQŒèÊY件的核心是可¾l´æŠ¤æ€§ã€‚可¾l´æŠ¤æ€§ä¸»è¦å°±ä½“现在可è¯ÀL€§å’Œæ‰©å±•æ€§ã€?/p>

[fangang]åQˆå¯è¯ÀL€§ï¼‰ä¸è¦¾~–写大段的代ç ?/p>

[vcycyv]Martin Fowler½Ž?从大ŒDµä»£ç æŠ½å–独立的æ–ÒŽ³•"叫做"extract method"åQŒè¿™æ˜¯å¸¸è§è€Œé‡è¦çš„重构手段。在他的refactor书里从技术层面做了详¾l†çš„阐述。分解的˜q‡ç¨‹ä¸­ï¼Œæ¯”较å®ÒŽ˜“形成技术障¼„çš„local variable. 引一ŒDµä¹¦é‡Œçš„话，专门讨论˜q™ä¸ªè¯é¢˜çš„：

â€?nbsp;    Copy the extracted code from the source method into the new target method.
â€?nbsp;    Scan the extracted code for references to any variables that are local in scope to the
source method. These are local variables and parameters to the method.
â€?nbsp;    See whether any temporary variables are used only within this extracted code. If so,
declare them in the target method as temporary variables.
â€?nbsp;    Look to see whether any of these local-scope variables are modified by the extracted
code. If one variable is modified, see whether you can treat the extracted code as a query
and assign the result to the variable concerned. If this is awkward, or if there is more than
one such variable, you can't extract the method as it stands. You may need to use Split
Temporary Variable and try again. You can eliminate temporary variables with
Replace Temp with Query (see the discussion in the examples).
â€?nbsp;    Pass into the target method as parameters local-scope variables that are read from the
extracted code.
â€?nbsp;    Compile when you have dealt with all the locally-scoped variables.
â€?nbsp;    Replace the extracted code in the source method with a call to the target method.

â€?nbsp;    Compile and test.

前两òq´çœ‹åˆîC¸€ä¸ªè®¨è®ºçš„很火的话题，说ä“Q意复杂的产品åQŒéƒ½èƒ½break into一¾pÕdˆ—的小æ–ÒŽ³•åQŒæ¯ä¸ªæ–¹æ³•è¡Œæ•îC¸­‘…过5行。当然没必要˜q™ä¹ˆç‹ ï¼Œä½†å¦‚果你真这么狠åQŒæˆ‘倒觉得没啥明昄¡š„坏处ã€?/p>

"而一些更有经验的½E‹åºå‘˜ä¼šé‡‡ç”¨å¦å¤–一¿Uä»Žä¸Šå¾€ä¸‹çš„¾~–写方式。当他们在编写程序的时候，每个被分出去的程序，可以暂时只写一个空½E‹åºè€Œä¸åŽÕd…·ä½“实现功能。当ä¸È¨‹åºå®Œæˆä»¥åŽï¼Œå†ä¸€ä¸ªä¸ªå®žçŽ°å®ƒçš„所有子½E‹åºã€‚采用这æ ïLš„¾~–写方式åQŒå¯ä»¥ä‹É复杂½E‹åºæœ‰æ›´å¥½çš„规划åQŒé¿å…åªè§æ ‘木不见森林的弊病ã€?˜q™ä¹Ÿæ˜¯ä¸€ä¸ªå¥½çš„实è·üc€?

提到˜q™ç§è‡ªä¸Šè€Œä¸‹çš„ç¼–½E‹æ–¹æ³•ï¼Œ™åÞZ¾¿æŽ¨è 《斯坦福大学开放课½E‹ï¼š¾~–程æ–ÒŽ³•ã€‹ã€‚这是一¾pÕdˆ—视频教程。google一下有很多地方可以下蝲或在¾U¿è§‚看，比如优酷http://v.youku.com/v_show/id_XMjE4NzQ0NDI0.html 在视频教½E‹é‡Œæ•™æŽˆä¹Ÿæ¼”½CÞZº†è‡ªä¸Šè€Œä¸‹çš„ç¼–½E‹æ–¹æ³•ã€?˜q™æ˜¯å…¥é—¨¾U§çš„教程åQŒæœ¬æ¥æƒ³é€šè¿‡å®ƒç»ƒ¾lƒå¬åŠ›ï¼ŒåŽæ¥å‘现˜q™è¯¾½E‹æ ¹æœ¬å°±æ˜¯å–œå‰§ç‰‡åQŒçœ‹çš„过½E‹ä¸€ç›´ç‹‚½W‘，教授牚w€—ã€?

跟可è¯ÀL€§ç›¸å…³çš„一个话题就是注释。近òq´æ¥ä¸€ä¸ªå¹¿æ³›è¢«æŽ¥å—的做法是åQŒå°½é‡é€šè¿‡ 避免大段代码 以及良好的变量命名达到可è¯ÀL€§ã€‚注释在˜q™ä¸ª˜q‡ç¨‹ä¸­è¢«æ·¡åŒ–了。我基本同意˜q™ç§åšæ³•åQŒç¨‹åºç»“构清晎ͼŒè‡ªè§£é‡Šçš„变量名都是重要的实践。变量名ž®½é‡ä¸è¦å†™ç¾ƒå†™ï¼Œå¦‚果写羃写的话，一定要æœ?strong>¾~©å†™å­—典有据可查。看spring的代码，可以发现很多¾cÕdæˆ–方法名åœ?0个字½W¦ä»¥ä¸Šã€‚大ŒD‰|³¨é‡Šå¾€å¾€æš—示½E‹åº¾l“构的不合理。不鼓励写过多注释的¾l“æžœž®±æ˜¯åQŒå‰©ä¸‹çš„注释都是重要不可或缺的，注释是程序的一部分åQŒéœ€è¦å’Œ½E‹åºä¿æŒä¸€è‡ß_¼Œä¹Ÿéœ€è¦è¢«¾l´æŠ¤ã€‚另一个基本而重要的原则是，要把public package protected privateæ–ÒŽ³•æŒ‰ç…§™åºåºå†™ã€‚更重要的、可讉K—®æ€§æ›´é«˜çš„æ–ÒŽ³•æ”‘Ö‰é¢ï¼Œž®½ç®¡eclipse里可以方便地在视图过滤非publicæ–ÒŽ³•ã€?

[fangang](可维护æ€?但是åQŒäº‹å®žå´ä¸ä¸€æ øP¼Œå¯ÒŽœºå…³çñ”‹Æ¡è®¡½Ž—的代码遍布整个™å¹ç›®åQŒç”šè‡Ïxœ‰äº›è¿˜å†™å…¥åˆîCº†é‚£äº›å¤æ‚çš„SQL语句中ã€?

[vcycyv] Domain Driven Disignå¼ø™°ƒåQŒdomain的逻辑要圈在一定边界中。往上不能爬到service, 甚至UI层。往下不能渗透到repository以下åQŒæ¯”如sql语句里ã€?Domain Driven Design的书åœ?a >˜q™é‡Œä¸‹è²ã€‚更多电子书可以看之前写的博å®?分äín十二本经典电子书

[fangang]ž®†ä¸“用代码提升äؓ通用代码

[vcycyv] ˜q™ä¸ª˜q‡ç¨‹å¤§å®¶éƒ½ä¼šé‡åˆ°ã€‚什么代码算通用代码òq¶ä¸å®ÒŽ˜“界定。过多的通用代码æ·ÒŽ²¡äº†çœŸæ­£æœ‰é€šç”¨æ„ä¹‰çš„方法，不èƒö的通用代码å®ÒŽ˜“造成代码重复。这个过½E‹æœ‰˜q™ä¹ˆå‡ ä¸ªæ–šw¢éœ€è¦æ³¨æ„ã€?

一åQŒé¿å…é‡å¤é€ è½®å­ã€?要对JDK常用的API以及¾lå…¸½W¬ä¸‰æ–¹çš„软äšg包有一定了è§?/strong>。ä‹D两个例子åQšå¤å…¸çš„singleton在JDK1.5之后可以用单一元素的enum表示åQŒè€Œä¸”不用考虑serializableçš„readresolve问题åQ?apache commons里的io, lang½{‰åŒ…提供了很多常用的API。我在我们的产品里，用到ioçš„FileNameUtilså’ŒExceptionUtils的一些方法。包括取文äšg后缀名，获取exceptionçš„root cause以及excepiton stackçš„å­—½W¦ä¸²ã€?要尽量重用可靠的½W¬ä¸‰æ–¹ä»£ç ï¼Œ 原因是你自己写的代码多半不如Sunå’Œapacheçš„äh好。更重要的是åQŒä½ è‡ªå·±å†™çš„每一行code都要自己¾l´æŠ¤ã€‚代码行数本íw«å°±æ˜¯ä»£ç ç»´æŠ¤é‡çš„一个因素。最˜q‘一两年疯狂地喜‹Æ¢åˆ é™¤ä»£ç ï¼Œä¼°è®¡å†å‘展下åŽÀLˆ‘ž®Þp¦è¢«åˆ é™¤äº†ã€?

二， ˜q˜æ˜¯domain为先ã€?strong>当你犹èõU一ŒD‰|¯”较“通用”的代码应该攑֜¨module里还是拿出来的时候，ž®½é‡˜q˜æ˜¯ä¿ç•™åœ¨module里吧。因为如果你犹èõU来，犹èõUåŽÖM¹‹åŽï¼Œå†›_®šå®ƒæ˜¯global的通用代码åQŒä¸‹ä¸€ä¸ªäh非常可能在module里找不到åQŒå°±è®¤äؓ没有˜q™ç§code,自己又写一遍。太‹È€˜q›çš„写一堆通用代码åQŒä¸€æ—¦ç»„¾l‡ä¸å¥½ï¼Œž®±æ²¡äººçˆ±åŽÖM»Žé€šç”¨ä»£ç é‡Œå¯»å®äº†ã€‚关于这一点，martin大叔有近似的阐述åQ?åœ?a >Patterns of Enterprise Application Architectureé‡?

A common concern with domain logic is bloated domain objects. As you build a screen to manipulate orders you'll notice that some of the order behavior is only needed only for it. If you put these responsibilities on the order, the risk is that the Order class will become too big because it's full of responsibilities that are only used in a single use case. This concern leads people to consider whether some responsibility is general, in which case it should sit in the order class, or specific, in which case it should sit in some usage-specific class, which might be a Transaction Script (110) or perhaps the presentation itself.

The problem with separating usage-specific behavior is that it can lead to duplication. Behavior that's separated from the order is harder to find, so people tend to not see it and duplicate it instead. Duplication can quickly lead to more complexity and inconsistency, but I've found that bloating occurs much less frequently than predicted. If it does occur, it's relatively easy to see and not difficult to fix. My advice is not to separate usage-specific behavior. Put it all in the object that's the natural fit. Fix the bloating when, and if, it becomes a problem.

三、通用代码一定要有整体设计。如果调用通用代码的那些invoker不完全在你控制的范围åQŒæ¯”如你写的½E‹åºæœ‰å…¶ä»–项目组在调用，那么你修改API的签名一定会被骂æ­Èš„。所以通用代码要思前惛_Ždesign清楚了才release.¾l“构清楚的通用代码也比较方便以后查找ã€?strong>好的½E‹åºæ€ÀL˜¯åˆ†å±‚的，通用代码要尽量往底层æ”?/strong>ã€?

[fangang]一个快速提高èÊY件质量的捷径ž®±æ˜¯åˆ©ç”¨è®¾è®¡æ¨¡å¼ã€?

[vcycyv]设计模式除了是一¿Uå·¥å…·ä»¥å¤–，学习、思考设计模式能扩展coding的思维方式。自å·×ƒ¹Ÿæ€È»“了一½‹‡åšå®?串讲23¿Uè®¾è®¡æ¨¡å¼?/a> ã€?

[fangang]拿一个员工工资系¾lŸæ¥è¯´å§ã€‚当人力资源在发放一个月工资的时候，以及¼›»èŒçš„员工肯定不能再发放工资了。在¾pȝ»Ÿè®¾è®¡çš„期初，开发äh员商量好åQŒåœ¨å‘˜å·¥ä¿¡æ¯ä¸­è®¾å®šä¸€ä¸ªâ€œç¦»èŒæ ‡å¿—”字ŒDüc€‚编写工资发攄¡š„开发äh员通过查询åQŒå°†â€œç¦»èŒæ ‡å¿—”äØ“false的员工查询出来，òq¶äؓ他们计算和发攑ַ¥èµ„。但是，随着˜q™ä¸ª¾pȝ»Ÿçš„不断ä‹É用，¾~–写员工½Ž¡ç†çš„开发äh员发玎ͼŒâ€œç¦»èŒæ ‡å¿—”字ŒDµå·²¾lä¸èƒ½æ»¡­‘›_®¢æˆïLš„需求，因而将“离职标志”字ŒDµåºŸå¼ƒï¼Œòq¶å¢žåŠ äº†ä¸€ä¸ªâ€œç¦»èŒæ—¶é—´â€å­—ŒD‰|¥½Ž¡ç†¼›»èŒçš„员工。然而，¾~–写工资发放的开发äh员åƈ不知道这æ ïLš„变更åQŒä¾ç„¶ä‹É用着“离职标志”字ŒDüc€‚显ç„Óž¼Œ˜q™æ ·çš„结果就是，软äšg¾pȝ»Ÿå¼€å§‹å¯¹¼›»èŒå‘˜å·¥å‘放工资了。仔¾l†åˆ†æžè¿™ä¸ªé—®é¢˜çš„原因åQŒæˆ‘们不隑֏‘玎ͼŒ¼‹®è®¤å‘˜å·¥æ˜¯å¦¼›»èŒåQŒåƈ不是“发攑ַ¥èµ„”èÊY件类应当完成的工作，而应当是“员工管理”èÊY件类应当完成的。如果将“获取非¼›»èŒå‘˜å·¥â€çš„ä»ÕdŠ¡äº¤ç»™â€œå‘˜å·¥ç®¡ç†â€èÊY件类åQŒè€Œâ€œå‘攑ַ¥èµ„”èÊY件类仅仅只是去调用，那么¼›»èŒåŠŸèƒ½ç”±â€œç¦»èŒæ ‡å¿—”字ŒD‰|”¹ä¸ÞZº†â€œç¦»èŒæ—¶é—´â€å­—ŒDµï¼Œå…¶å®žž®×ƒ¸Žâ€œå‘攑ַ¥èµ„”èÊY件类毫无关系。而作为“员工管理”的开发äh员，一旦发生这æ ïLš„变更åQŒä»–当然知道åŽÖM¿®æ”¹è‡ªå·Þq›¸åº”的“获取非¼›»èŒå‘˜å·¥â€å‡½æ•ŽÍ¼Œ˜q™æ ·ž®×ƒ¸ä¼šå‘生以上问题ã€?

[vcycyv]哈哈åQŒæˆ‘喜欢˜q™ä¸ªä¾‹å­ã€‚DDD的核心思想ž®±æ˜¯˜q™ä¸ªã€‚当然DDD的理è®ø™¿˜æœ‰ä¸€äº›å…·ä½“的实践。Eric Evan在他的DDD书里讲了一个cargo的例子，当时我还找了一下代码，没找刎ͼŒä»Žfangang的博客评论里居然发现哪里能找åˆîC»£ç äº†åQ?a title="http://dddsample.sourceforge.net/" >http://dddsample.sourceforge.net/, ˜q˜æ²¡æ¥å¾—及具体看。以后有æœÞZ¼šæ·±å…¥äº†è§£ä¸€ä¸‹ã€?

[fangang]åQˆä»£ç å®¡æŸ¥ï¼‰ 被审查后的代码如果还出现¾~ºé™·åQŒå®¡æŸ¥è€…应当负有责ä»?

[vcycyv] ˜q™ä¸ª¾pÕdˆ—的最后一½‹‡æ–‡ç« ä¸»é¢˜æ˜¯ä»£ç å®¡æŸ¥ã€‚作者所说的最佛_®žè·µå¾ˆæœ‰é“理，但不是在ä»ÖM½•çŽ¯å¢ƒä¸‹å¯æ“ä½œæ€§éƒ½å¼ºçš„。我不知道最佛_®žè·‰|˜¯ä»€ä¹ˆï¼Œä½†æˆ‘觉得有一些问题是值得注意的ã€?

一ã€?strong>代码审查的范围要ž®ï¼Œæœ€å¥½æ˜¯one-oneçš?/strong>åQŒè·Ÿ¾l©æ•ˆæ²¡æœ‰å…³ç³»åQŒèŒƒå›´å°å¯ä»¥ä¿è¯å®¡æŸ¥ä¸ä¼šå¤ªä¼¤â€œé¢å­â€ï¼Œå¦åˆ™ä¼šåª„响团¾l“氛围ã€?

二ã€?strong>审查者在指出错误的同æ—Óž¼Œä¸€å®šè¦è¯´å¦‚何修正问é¢?/strong>。我非常非常反感那种善于用大道理指出别äh错误åQŒè‡ªå·±å´æŠŠé”™è¯¯çŠ¯å¾—更夸张的那¿Uäh。如果你自己没有更好的解å†Ïx–¹æ¡ˆï¼Œž®±åˆ«è¯´é‚£æ˜¯é—®é¢˜ã€?

三、代码审查制度的推行以良好的团队氛围为前提。大安™ƒ½æ˜¯äؓ了äñ”品着惻I¼Œ˜q™æ ·ä»£ç å®¡æŸ¥æ‰ä¸è‡³äºŽæ‰¯çš®ã€?

四、关于审查者的责ä“Q。我同意fangang说的"被审查后的代码如果还出现¾~ºé™·åQŒå®¡æŸ¥è€…应当负有责ä»?, 但是谁来˜q½ç©¶è´£ä“QåQŒå¦‚何界定责任，怎么˜q½ç©¶è´£ä“Q呢？呵呵åQŒè¿™ä¸ªææ€•ä¸å¥½æ“ä½œã€‚代码审查显然不能杜¾ldefect, 但是明显的设计，¾~–码错误是应该看到的åQŒä½†æ€Žä¹ˆåˆç®—"明显"呢。èÊY件本íw«ä¸åƒæ•°å­¦é‚£æ ·ä¸¥æ û|¼Œå®ÒŽ˜“界定问题。纪律在软äšg行业作用有限åQŒå›¢é˜Ÿæ°›å›´æ¯”¾Uªå¾‹é‡è¦ã€‚但怎么营造好的团队氛围又是一个太宽泛的问题ã€?

˜q™ä¸ªå¸–子很牛åQ?/p>

http://www.itpub.net/viewthread.php?tid=1313696&extra=&page=1

我的观点是，外键在初始阶ŒDµèƒ½åŠ çš„都加上，只有˜q«ä¸å¾—已的时候才disable或drop掉。遇到性能瓉™¢ˆçš„时候，ž®½é‡é‡‡ç”¨å…¶å®ƒæ–¹å¼è°ƒä¼˜åQŒè€Œä¸è¦è½»æ˜“牺牲掉外键。有外键¾U¦æŸçš„时候，写程序的¼‹®ä¼šæœ‰çº¦æŸï¼Œä½†ä»Žç›´è§‰ä¸Šè¯´˜q™ç§¾U¦æŸä¸€å®šç¨‹åº¦ä¸Šæ­ç¤ºäº†è®¾è®¡æˆ–实现上不合理的地斏V€‚带着外键写出来的应用更們֐‘于严谨。äñ”品上¾U¿ä¹‹å‰å¦‚果确实需要通过牺牲外键辑ֈ°æ€§èƒ½ä¸Šçš„优化åQŒå†æ¡ç›¸å¯¹ä¸é‡è¦çš„外键废弃掉åQŒåŒæ—¶è¦æŠŠè¿™ä¸ªdocument下来åQŒä¸‹‹Æ¡é‡åˆ°æ•°æ®ä¸ä¸€è‡´é—®é¢˜çš„时候，是个¾U¿çƒ¦ã€‚两点说明：1. 我们在做的一个项目确实是ž®é¡¹ç›®ã€?nbsp; 2. 我得承认我最˜q‘三òq´å¼€å‘都不用关系型数据库åQŒè²Œä¼?no sql那么nbçš„key-value pair存数据，其实˜q™ä¸‰òq´åœ¨æŒä¹…层上很多¾U ç»“。如果我说的不对åQŒè¯·æŒ‡æ­£åQ?/u>