[elephant-devel] Re: export #:db-error ?
Ian Eslick
eslick at csail.mit.edu
Sat May 5 23:48:45 UTC 2007
db-error is a general condition which says there was an internal
error in the db (something that is not likely the fault of the
user). I've started adding other conditions that are problem-
specific and refer to things the user has done in error. As part of
cleanup, they should inherit from a common source so you can
inhibit / handle all elephant conditions as necessary. Please add
comments to an existing ticket or a new tickets to describe your
thoughts about what should be done here.
Ian
On May 5, 2007, at 7:41 PM, Mac Chan wrote:
> So in the current source code DB-ERROR is wrap around with (eval-when
> (:compile-toplevel :load-toplevel))
>
> I guess the question is whether the application programmer need to
> guard against database error when using any of the db operation api.
>
> Thanks.
>
> On 5/5/07, Mac Chan <emailmac at gmail.com> wrote:
>> I noticed a warning "DB-ERROR is not a valid type" when I compile the
>> blog-example.
>>
>> (handler-case
>> (with-transaction ()
>> (make-instance 'blog-entry
>> :date date
>> :title title
>> :text text))
>> (db-error () nil))
>>
>> It so happens that I still have the old elephant source code (I
>> simply
>> untar the new code into the same directory)
>>
>> When I do a grep on all the source I find that in the original
>> src/sleepycat.lisp it exports a bunch of symbol which includes
>> #:db-error
>>
>> Is this symbol supposed to be exported?
>>
>> Thanks.
>>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel
More information about the elephant-devel
mailing list