<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="0.92">
<channel>
	<title>Dryice Liu's Blog</title>
	<link>http://dryice.name/blog</link>
	<description></description>
	<lastBuildDate>Tue, 31 Aug 2010 12:01:11 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Never think your password is complicated enough</title>
		<description>Last week I was asked to help a friend to check out his server that has been hacked. First I was thinking some kind of PHP leak or SQL injection. But I was wrong. The crack uses some kind of SSH user/password scanner and got his root password.

I find this ...</description>
		<link>http://dryice.name/blog/freebsd/never-think-your-password-is-complicated-enough/</link>
			</item>
	<item>
		<title>sqlite doesn&#8217;t support more than one primary key in one table</title>
		<description>This cost me several hours today.

Postgresql support multiple primary keys in one table, and I took granted that sqlite does the same thing when I did some prototype today.

And they have a good reason explained in the SQLite CVSTrac.

The odd thing is, if I specify two primary keys in sqlite, ...</description>
		<link>http://dryice.name/blog/postgresql/sqlite-doesnt-support-more-than-one-primary-key-in-one-table/</link>
			</item>
	<item>
		<title>sqlobject in one file</title>
		<description>Looks if two SQLObject class got reference to each other, i.e, ForeignKey, they should stay in the same file. Else the generated reference column name will get messed up and causing problem. This is where I wasted 3 hours today :(

Also the column name should be in mixedCase instead of ...</description>
		<link>http://dryice.name/blog/python/sqlobject-in-one-file/</link>
			</item>
	<item>
		<title>don&#8217;t create table with name ends &#34;_seq&#34;</title>
		<description>postgresql use this kind of table to keep track of sequence.

Share This
 </description>
		<link>http://dryice.name/blog/postgresql/dont-create-table-with-name-ends-_seq/</link>
			</item>
</channel>
</rss>

