From: Jamis Buck <jgb3@...>
Date: 2004-07-04T07:11:00+09:00
Subject: Re: SQLite/Ruby update pending

Ara.T.Howard wrote:

> sounds good.  hopefully you know that it goes without saying that you 
> can take
> arrayfields.rb and distrbute it with sqlite if you ever want too...

Thanks, Ara. I appreciate that. However, I always worry when doing that, 
since if I package it with one version of arrayfields, and somewhere 
down the road I forget to update arrayfields when you come out with a 
new version, it could wind up that a user will have multiple 
(potentially incompatible) versions of arrayfields installed...which 
gets ugly.

> a dedicated error for SQLITE_BUSY!  it would be great to be able to
> 
> begin
>   db.execute sql
> rescue SQLite::Busy
>   retry unles too_many_retries or timeout
> end

Done! The exception is SQLite::BusyException. :) I'd been meaning to do 
that anyway--thanks for reminding me!

Other exceptions are also defined, such as SQLite::LockedException, 
SQLite::SQLException, and so forth. (Basically, each valid return code 
defined by the sqlite API is now encapsulated in an exception class.)

Anything else? :)

-- 
Jamis Buck
jgb3@email.byu.edu
http://www.jamisbuck.org/jamis

ruby -ropenssl 
-e'k="01234567";p((c,c.padding,c.iv,c.key=OpenSSL::Cipher::BF.new,0,k,k*2)[0].decrypt.update("1A81803C452C324619D319F980D5B84DBB45FC0FE2BAA045".scan(/../).map{|n|n.to_i(16).chr}.join))'