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

[Mario R. <ma...@ru...>]

Hello,

...

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=20=

> model
> that uses 'timestamp' switches back to 'datetime' when MySQL is used.=20=

> The
> reason for this is that the datatype 'timestamp' has an=20
> automatic-update
> feature on MySQL that I cannot handle --the framework just cannot=20
> foresee
> whether it has been changed or not.

That's quite unfortunate. However, it also makes me ask why does the XML
model include the adaptorName and connectionDictionary attributes?
These are specifying mysql or postgres... so the rest of the model defn
should comply? I know, it should be independent, but then also both=20
these
attributes should not appear here (in any case they make the model, as=20=

is,
not portable).

...

>> Evaluating: DROP TABLE WRITER
>> Couldn't evaluate expression DROP TABLE WRITER. Reason:
>> libpq.OperationalError:ERROR:  Cannot drop table writer because other
>> objects depend on it
>>          Use DROP ... CASCADE to drop the dependent objects too
>
> Although logical, that's amazing, I never get this with postgres=20
> 7.2.1. I've
> to check that, and see if I can find a common behaviour. If someone as=20=

> any
> hints about this, please share!

No ideas, but why is it logical?
...

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

As of a couple of days I am running python 2.2.2, built locally.

> -- S=E9bastien.

Thanks again for the fixes.
Now I need to actually try something more real with it...

Cheers, mario=