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

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

        Hi,

> > I suggest that you edit
> >   tests/testPackages/AuthorBooks/model_AuthorBooks.xml and
> ...
> >   so that it says (change externalType DATETIME to TIMESTAMP):
>=20
> Changing datetime to timestamp works perfectly.  From a clean databas=
e, the
> following sequence of tests run OK (except for dropping of non-exista=
nt
> tables):

Ok, fine. I've just made some changes on the CVS tree (see CHANGES), but
there's still some work to be done within the test-suite so that the mo=
del
that uses 'timestamp' switches back to 'datetime' when MySQL is used. T=
he
reason for this is that the datatype 'timestamp' has an automatic-update
feature on MySQL that I cannot handle --the framework just cannot fores=
ee
whether it has been changed or not. Details are in
MySQLAdaptorLayer.MySQLSQLExpression and at:
http://www.mysql.com/documentation/mysql/bychapter/manual_Reference.htm=
l#DATETIME

> However, running the tests a 2nd time gives errors, namely because
> the now existent tables cannot be dropped. The first error occurs in =
the
> 2nd script step, for which I am including the output below. This shou=
ld
> probably be corrected.
> [...]
> # output log:
> Evaluating: DROP TABLE WRITER
> Couldn't evaluate expression DROP TABLE WRITER. Reason:=20=20
> libpq.OperationalError:ERROR:  Cannot drop table writer because other=
=20=20
> objects depend on it
>          Use DROP ... CASCADE to drop the dependent objects too

Although logical, that's amazing, I never get this with postgres 7.2.1.=
 I've
to check that, and see if I can find a common behaviour. If someone as =
any
hints about this, please share!

> I am also suggesting a slightly modified tests/README...

Well, it seems a lot clearer than what I wrote, and it now replaces the=
 former
one. Thanks!

  Last, can you tell which python version you're currently using?

-- S=E9bastien.