FYI, here's another data point.
I got the latest source from darcs and ran the test on fedora fc6 +
lispworks 32bit 5.0.2
All tests passed but there were some warning (I've seen similar
warnings from the dbd backend).
However, the test took almost one hour to finish, is that normal?
ELE-TESTS
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 <[EMAIL PROTEC
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 happen
Hi,
Could you add (pushnew :elephant *features*) somewhere in the source?
This way I can easily comment out a block of code when elephant is not
available.
Thanks.
(defun start ()
#+elephant
(progn
(ensure-directories-exist (second *blog-store-spec*))
(open-store *blog-store-spec*))
.
On 4/22/07, Ian Eslick <[EMAIL PROTECTED]> wrote:
You can access the class index cursor using:
'make-class-cursor' for all instances and
'make-inverted-cursor' on a specific slot index
You can also use the convenience macros:
'with-inverted-cursor' and 'with-class-cursor'
Thanks. That worked. I
Hi Ian,
On 4/21/07, Ian Eslick <[EMAIL PROTECTED]> wrote:
This example could be done even more cleanly using the class indexing
facilities. If you feel inclined to experiment with them, this would
be a good contribution to improve the example.
Actually it turned out to be an interesting exerc
Hi all,
I converted the blog example to use hunchentoot.
Please see the attached file.
It's very cool to see elephant in action.
Cheers,
-- Mac
hunchentoot.blog.lisp
Description: Binary data
___
elephant-devel site list
elephant-devel@common-lisp.ne
