(render-blog Ng Pheng Siong)

05 December 2004

lsqlite3 / lsqlcrypt3

I was getting ready to publish lsqlite3 (previously mentioned) and lsqlcrypt3, its SQLcrypt-based counterpart. Simultaneously, I was talking to my 8 year-old who was asking me to play a game of chess with him or something. I got distracted and typed "del *.lisp" when I meant "dir *.lisp". All gone! Gah! So I went and played some chess. (I have a copy of lsqlite3 somewhere. lsqlcrypt3 needs to be recreated.)

Tomorrow (Sunday) I will update M2Crypto for Python 2.4 and attempt to fix some of the reported bugs, so lsqlite3/lsqlcrypt3 will have to wait till Monday or later.

Posted by ngps at 00:06 | Comments (3) | Trackbacks (0)

Comments

Re: lsqlite3 / lsqlcrypt3

This is one reason why I always use cvs (preferably on another machine) to back up development, and keep the distance between commits short enough to recover from any disaster.

Posted by: Paul Dietz at December 05,2004 00:14

Re: lsqlite3 / lsqlcrypt3

Good advice.

In this case I was working on my notebook in the living room, away from the "computer centre" at home. Ah well. I'm going to get a wireless router pronto. (Whee, that's another whole bunch of stuff to blog about, what. ;-)

Posted by: Ng Pheng Siong at December 05,2004 02:12

Re: lsqlite3 / lsqlcrypt3

Release early -- release often. :)
If you have 15 previous releases on your website, it's easy to start over when you trash your homedir. :)

Posted by: Randall Randall at December 05,2004 02:53

Trackbacks

Please send trackback to:http://sandbox.rulemaker.net/ngps/170/tbping

There is no trackback.