随着2015年即将过去,我在考虑新的一年要不要开始在电脑上写日记。。
为什么要用电脑写日记?
一来,自己的字太潦草,以后不好辨认。
二来,纸质日记本来回拿着确实不大方便。
三来,担心被盗。
四来,以后可以用电子版做统计。
为什么要用写纸质日记?
- 现在用手写中文的机会越来越少。
嗯,确实需要在2016年前考虑考虑了。
PS: 伪装者真好看!
Github小标志让街车稍稍与众不同^^ |
现在车的右屁股已经不是那么光滑了TAT |
去年面UBER的时候拍的,那天下雨 |
烤鱼超过瘾 |
Dialog dialog = new Dialog(getActivity());http://stackoverflow.com/questions/9516287/android-click-event-outside-a-dialog
Window window = dialog.getWindow();
window.setFlags(WindowManager.LayoutParams.FLAG_NOT_TOUCH_MODAL,
WindowManager.LayoutParams.FLAG_NOT_TOUCH_MODAL);
window.clearFlags(WindowManager.LayoutParams.FLAG_DIM_BEHIND);
dialog.setCanceledOnTouchOutside(false);
dialog.show();
CSE132b的milestone4和milestone5的due
体检
master project的presentation
CSE132b的final的due
争取今天把132b的milestone4和5做完。
这个是比较好的TRIGGER讲解LINK
英文原版LINK
In computing, a materialized view is a database object that contains the results of a query. For example, it may be a local copy of data located remotely, or may be a subset of the rows and/or columns of a table or join result, or may be a summary based on aggregations of a table's data.The process of creating a materialized view is sometimes called materialization. It is sometimes described as a form of precomputation. As with other forms of precomputation, materialized views are typically created for performance reasons, i.e. as a form of optimization.
In any database management system following the relational model, a view is a virtual table representing the result of a database query. Whenever a query or an update addresses an ordinary view's virtual table, the DBMS converts these into queries or updates against the underlying base tables. A materialized view takes a different approach in which the query result is cached as a concrete table that may be updated from the original base tables from time to time. This enables much more efficient access, at the cost of some data being potentially out-of-date.
Materialized views are disk based and update periodically base upon the query definition.
Views are virtual only and run the query definition each time they are accessed.
Also when you need performance on data that don't need to be up to date to the very second, materialized views are better, but your data will be older than in a standard view.
临时表在会话结束时自动删除, 或者是(可选)在当前事务的结尾(参阅下面的 ON COMMIT)。 现有同名永久表在临时表存在期间在本会话过程中是不可见的, 除非它们是用模式修饰的名字引用的。 任何在临时表上创建的索引也都会自动删除。
CREATE TRIGGER 创建一个新的触发器。 触发器将与指定表关联并且将在特定事件发生时执行声明的函数 funcname。PostgreSQL 8.1 中文文档
[code language="sql"]CREATE [ CONSTRAINT ] TRIGGER name { BEFORE | AFTER |CREATE TRIGGER name { BEFORE | AFTER } { event [ OR ... ] }
ON table [ FOR [ EACH ] { ROW | STATEMENT } ]
EXECUTE PROCEDURE funcname ( arguments )
[/code]
name
赋予新触发器的名称。它必需和任何作用于同一表的触发器不同。
BEFORE
AFTER
决定该函数是在事件之前还是之后调用。
event
INSERT,DELETE 或 UPDATE 其中之一。 它声明击发触发器的事件。多个事件可以用 OR 声明。
table
触发器作用的表名称(可以用模式修饰)。
FOR EACH ROW
FOR EACH STATEMENT
这些选项声明触发器过程是否为触发器事件影响的每个行触发一次, 还是只为每条 SQL 语句触发一次。如果都没有声明, FOR EACH STATEMENT 是缺省。
funcname
一个用户提供的函数,它声明为不接受参数并且返回 trigger 类型。
允许你为 "old" 和 "new" 行或者表定义别名,用于定义触发器的动作(也就是说, CREATE TRIGGER ... ON tablename REFERENCING OLD ROW AS somename NEW ROW AS othername ...)。
回调函数并非是一种特殊类型的对象,其实就是普通的函数,但是被作为其他函数的参数传递,在某个时刻才会被选择性地使用。
由于回调函数会在什么时候被执行,可能是不确定,甚至也可能永远不会被执行。而且在上面的这种情况下,这个回调函数甚至要在未来的某个时候才会执行,这就有了一个“异步”的感觉,也就是说代码不是从上到下依次执行,前面的代码执行完毕后面的才会执行。
In the first regex, each space character is being replaced, character by character, with the empty string.
In the second regex, each contiguous string of space characters is being replaced with the empty string because of the+
.
When using dashboards, you wrap the actual charts (the map, the table) in google.visualization.ChartWrapper instances.
HTML5 的local storage 是通过浏览器在本地存储的数据。
第二次路考,STOP SIGN停留过久(我跑神了),挂了。
第三次路考,下坡忘记减速,挂了。
第四次路考,变道没有看到盲点有车,挂了。
第五次路考,右转入道在STOP SIGN处急着转弯没有看车,挂了。
此次考驾照,共计消费
37+37(笔试)+6+6(2,3次补考)+7+7(5,6次补考)+210(教练练车)=310刀
等我渐渐长大之后,我发现原来出国、读名校、念博士、买房、泡美女、进大企业等等事情,就像钱钟书先生所谓的“出水痘”一样,出过之后就产生了免疫力,之后便不再惦念 了。这个过程其实是破除迷信的过程,你会发现,原来向往乃至崇拜的价值,其实也不值一提。自信若建立在这些水痘上,真就成了自卑了