Hello, Philippe!
Many thanks for your comments about this tests.
I'm posting this message instead of Vyacheslav. His original message was
banned by SPAM-bot of sourceforge :) (What he must do in this case?)
> Roman Simakov [08-07-01 11.23] :
>
>> > I can send you them before commit but I think it's not critical if
>> you > review them after commit.
>>
> I see that they are committed, nice
>
> Just two point :
>
> can you use :
> #Create second connection - update detail table
> con_detail = kdb.connect(
> dsn=dsn.encode(),
> user=user_name.encode(),
> password=user_password.encode()
> )
>
> instead of :
> #Create second connection - update detail table
> con_detail = kdb.connect(
> dsn=dsn,
> user='SYSDBA',
> password='masterkey'
> )
>
>
Done.
> And seems that a lot of tests are ok for target before 2.5
> so can you change target for all tests that are also ok for 2.x ?
>
Done. But I think in this case we will have a set of separate test cases
for 2.x
engine and we can't see full image about FK functionality.
And what about full test suite for reference integrity in firebird? This
features are not checked full in QM test now.
I think we can develop tests for full checking this features. But this
problem is very important and I think it would be very good to discuss
all possible test cases. Can anybody help as with it? May be use SQL
standard to gather test cases? Are there other ideas?
> Thanks
> -- Philippe Makowski
Regards
Vyacheslav Ozherelyev
Red Soft Corporation
|
