[Monetdb-developers] Key constraints and optimizers...

Sjoerd Mullender sjoerd at acm.org
Tue Jul 31 10:06:16 CEST 2007

Romulo Goncalves wrote:
> Romulo Goncalves wrote:
>> Stefan Manegold wrote:
>>> On Tue, Jul 31, 2007 at 02:25:04AM +0200, Romulo Goncalves wrote:
>>>> Dear developers....
>>>> I was checking the status of the SQL test web-site (cvs branch) and I 
>>>                                                      ^^^^^^^^^^^^
>>> guess you mean CVS development trunk (i.e., "Current"), right?
>>> (we use "branch" usually only for the "Stable" release branch ...)
>> Ups, you are right.
>>>> found some red ones.
>>>> In the test src/test/BugConstraint/delete_primarykey_1643845.sql
>>>> If I run the normal Mtest the test is red (the err output).
>>>> The constraint error given is for the foreign key and not for the 
>>>> primary key (as in the stable output).
>>>> If I ran with M4 the test is green the same happens if I set the 
>>>> optimizers off.
>>>> So we can conclude that the reason for this test being red are the 
>>>> optimizers and nothing else in SQL module.
>>> Most failing SQL/5 tests are due to Martin's recent partition optimizer
>>> changes on Friday Jul 27 2007 --- just like the compilation problems in M5
>>> ---; hence, yes it's M5 only, and related to / cause by optimizers. Guessing
>>> from Martin's checkin comments I think he's aware of these problems...
>>>> I tried to give a look to see which optimizer is breaking the test, but 
>>>> no results. Tomorrow I will continue.
>>>> I also think that all the tests that are red (the ones related with 
>>>> primary keys) are due this problem.
>>>> Should I open a bug or this is enough? Because it is an existent test 
>>>> that is red ;)
>> Martin is aware of the problem, but in any case I will open the bug for 
>> better control.
> Before to do a mistake (as usual after vacations) should I open a bug 
> for SQL (because the tests broken are from SQL module) or for M5 
> (because the code that breaks the tests is from M5) ?
> I would bet in the first one, right?

It doesn't really matter.  If it incorrect it will be fixed (or should
be anyway).  If you think the bug is in SQL, report it as SQL bug.  If
you think it is in M5, report as M5 bug.  And if you don't know, report
it somewhere.  Anywhere.

Sjoerd Mullender

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 370 bytes
Desc: OpenPGP digital signature
URL: <http://www.monetdb.org/pipermail/developers-list/attachments/20070731/0e605bf9/attachment.sig>

More information about the developers-list mailing list