Paul McNett wrote: > Uwe Grauer wrote: >> Uwe Grauer wrote: >>> The data type of field jobid from table dabo_unittest in the database >>> dabo_unittest on server dabodev.com changed to double precision. >>> Why is that? >>> The script create_firbird_test.sql says it should be numeric(18, 0). >>> Did you change the database? >>> >>> Uwe >> Paul, >> >> did you see the obove post? > > Yes, I just don't know what to do about it and haven't had time to look > into it yet. >
That doesn't matter. People spend there time however they can/want. >> I saw that the tests work with a double. > > You are saying that pk and jobid in test_dCursorMixin is coming back as > a double instead of a long? > Yes. I also don't know who changed it. I thought that it was you, because you commited a change to the firebird tests. The pk and jobid got changed to type double (whoever did this). May be we have to protect the test databases in the future. >> But just changeing the tables metadata to let the tests pass wouldn't >> help to get it right in dabo. > > Agreed. I didn't do this, did I? The tests as they stand don't check for > datatype of the pk, although they should. > >> Btw, the createscript for the firebird test database wasn't changed. >> It still says that the pk and the jobid should be Numeric(18,0). > > Either the database got created from a script other than > dabo/db/test/create_firebird_test.ddl, or dbFirebird.py is incorrectly > identifying and converting the types. I suspect the latter. It got recreated or changed by whoever that was. > I'll try to look into this this week, but no promises. > Now something for planning. Do you think we should change the metadata for other databases too? This way we could find a structure which allows us to have less differences for the tests. Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
