I would like to know if it is a known Bug to MaxDB 7.6.00.10 for windows that the DB-instance will be stopped when using 'drop view' with 'restrict'?
The following code results in a stopped instance on my MaxDB-installation: create table tbl_1 ( id int, number int, primary key(id)) // insert into tbl_1 values (1,1) // insert into tbl_1 values (2,2) // create view view_tbl_1 as select number from tbl_1 // create synonym syn_view_tbl_1 for view_tbl_1 // select * from syn_view_tbl_1 // drop view view_tbl_1 restrict -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
