<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
On Wed, 2007-03-07 at 02:23 +0100, Frank Schorr wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#000000">(asdf:operate 'asdf:load-op :elephant)</FONT></TT><BR>
<TT><FONT COLOR="#000000">(asdf:operate 'asdf:load-op :ele-clsql)</FONT></TT><BR>
<TT><FONT COLOR="#000000">(asdf:operate 'asdf:load-op :clsql-postgresql-socket)</FONT></TT><BR>
<TT><FONT COLOR="#000000">(asdf:operate 'asdf:load-op :elephant-tests)</FONT></TT><BR>
<TT><FONT COLOR="#000000">(ele-tests::do-backend-tests '(:clsql (:postgresql-socket "localhost" "clsql-tests" "postgres" "$postgres%")))</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
<BR>
I suspect that if you "dropdb" and re-"createdb" your test database, you will be green. I know that is not helpful if you have data that you have to preserve. I have successfully upgraded the complex database that backs my company: <A HREF="http://konsenti.com">http://konsenti.com</A> using the latest version of Elephant, but Ian suggests that this not be tried until he formally announces the Beta test.<BR>
<BR>
Ian and are are committed to successful upgrade processes; starting one major release ago we began promising that anyone who build a database with Elephant would be able to upgrade as we upgrade versions. However, this process is inherently a little rougher and harder to test than a clean test.<BR>
<BR>
Let me know if your system passes the tests when you start from a clean DB. If it doesn't, I will re-study the issue somehow.<BR>
<BR>
I don't believe the BDB tests interfere at all with the SQL tests; I habitually do both and have never had a problem like that.
</BODY>
</HTML>