Hi Listmembers, I think that I found a bug once again in MaxDB 7.6.00.12 (Windows):
User Mona creats a new schema 'SCHEMA1' and places some basetables in it. Mona gives DBAdmin the right to insert and drop things in the new schema: 'GRANT DROPIN, CREATEIN ON SCHEMA1 TO DBADMIN' Now DBAdmin creates a new view: 'CREATE OR REPLACE VIEW SCHEMA1.VIEW_BESTELUNGEN ... That ist the point when something goes wrong: The View-Table is not assigned to SCHEMA1. It is assigned to schema DBADMIN!? There is no errormessage by MaxDB if a user tries to insert a view into a schema he does not own the CREATIN-Privilege - it is assigned to the users schema although the create view-statement defines an other schema!? There is a workaround: It seems that view-tables are always assigned to the current schema, so the trick is to switch the schema before creating the new view: SET CURRENT_SCHEMA = SCHEMA1 // CREATE OR REPLACE VIEW SCHEMA1.VIEW_BESTELLUNGEN ... Can someone official please confirm this bug to me? Thanks & Regards -- 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]
