Bugs item #1975011, was opened at 2008-05-27 16:50 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1975011&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tests Group: SQL 2.24 >Status: Closed >Resolution: Fixed Priority: 6 Private: No Submitted By: Stefan Manegold (stmane) Assigned to: Niels Nes (nielsnes) Summary: SQL/4: tests in src/test/Update_Delete_action/ fail with M4 Initial Comment: With the (supposedly deprecated) MonetDB4 server, SQL tests in sql/src/test/Update_Delete_action/Tests/ fail possibly due to not properly dropped table(s): http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests4103/GNU.64.64.d-Fedora8/src_test_Update_Delete_action/delete_no_action.err.00.html These tests do work fine with the MonetDB5 server: http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests5103/GNU.64.64.d-Fedora8/src_test_Update_Delete_action/delete_no_action.err.00.html ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2008-05-29 08:35 Message: Logged In: YES user_id=572415 Originator: YES Thanks to Niels' fixes, these tests work fine, again. ---------------------------------------------------------------------- Comment By: Romulo Goncalves (romulog) Date: 2008-05-27 18:05 Message: Logged In: YES user_id=1498628 Originator: NO I got an example for you: create table t1 (id int, name varchar(1024), PRIMARY KEY(id)); create table t2 (id int, age int, PRIMARY KEY (id), FOREIGN KEY(id) REFERENCES t1(id)); -- ON DELETE CASCADE); insert into t1 values(1, 'monetdb'); insert into t1 values(2, 'mon'); insert into t2 values(1, 23); insert into t2 values(2, 24); drop table t2; drop table t1; If you now restart the mserver4 (stable optimized compilation) and create the same tables you will see that the tables are still there (or only the catalog information). However, if you invert the insertion order for t1: insert into t1 values(2, 'mon'); insert into t1 values(1, 'monetdb'); Everything starts to work again... Crazy?!?! :D Only MonetDB can give you these kind of challenges... Romulo ---------------------------------------------------------------------- Comment By: Romulo Goncalves (romulog) Date: 2008-05-27 17:13 Message: Logged In: YES user_id=1498628 Originator: NO I do not have M4 to solve the problem, but this might help... These are the only 3 tests that might create the problem because they are the ones using table t3... ./null.sql ./BugTracker/Tests/alter_table_add_fkey.SF-1737668.sql ./add_column_with_seq.sql Romulo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1975011&group_id=56967 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
