>> I tried to play around with different mappings e.g. map TIME to
>> timestamp in the database etc. but still no success. The Unit Tests
>> keep failing (I'm still looking into details).
>>
>> So I guess it comes down to the question if we'll fix the unit tests
>> and who'll do it
>
> I volunteer to look at this.
Good. Just let me know when you're ready to run the testsuite against
PostgreSQL.
> But if we make DATE_OF_BIRTH to be a DATE (as it should be), the next
> logical step is to add more entities with TIME and TIMESTAMP columns
> just to test how this works with various databases. I guess I can create
> a separate entity with all 3 types of columns present.
Don't forget EXHIBIT's opening_date and closing_date which were TIME so
far. I guess this is wrong as well. They could be timestamps ...
-dirk
This archive was generated by hypermail 2.0.0 : Wed Feb 05 2003 - 22:58:45 EST