Re: [Modeling-users] Installation tests failure - osx, pypgsql

[Sebastien B. <sbi...@us...>]

        Hi,

> the tests for modeling 0.8.1 fail on this OSX machine.  I am of course
> using pypgsql as the preferred adaptor -- thanks!  I try to follow the
> sequence of commands in tests/README, and include the log below.

  Thanks for pointing out the tests/README file, I didn't remember
  me writing it!

> Points to note: I created an empty db manually called "AUTHOR_BOOKS",
> because there was another error previously (do not have the log for
> it).
> If this must be done manually, then this should be pointed out in the
> installation doc.

  Yes, you're right, databases should be created before executing the
  script w/ the option '-r'. Two DBs should be created:
    "AUTHOR_BOOKS" (test_EditingContext_Global.py) and
    "STORE_EMPLOYEES" (test_EditingContext_Global_Inheritance.py)
  I'll update the README file.

> Also, all other locations where name/password/otherinfo should be
> specified -- in the XML models?

  These parameters do not need to be changed in the xml-models, you just
  need to change settings in file tests/test.cfg

  About errors you observed:

> Evaluating: DROP TABLE WRITER
> Couldn't evaluate expression DROP TABLE WRITER. Reason:=20=20
> libpq.OperationalError:ERROR:  table "writer" does not exist

  These errors are due to the fact that the database has just been
  created, so it is empty; these statements just try to wipe out any
  tables, PK and FK constraints and sequences that may exists in the
  database, just before (re-) creating them, hence you see them fail.
  This should be changed to the simpler 'DROP DATABASE' statement.

  Errors during the '-r' phase can be safely ignored if the databases
  are correctly intialized ; so if the tests pass when the '-r' option
  is NOT active, everything is ok.

However I just had a look at the test_EditingContext_Global.py and it
seems that I forgot to commit some changes that can make the following 2
tests fail: test_06_deleteRule_nullify(), and test_999_customSQLQuery()
w/ pypgsql. I need to check that, I'll write back when I have some news
about that.

  Thanks for reporting, tell me if you get more errors.

-- S=E9bastien.