Re: Import bug

"Howard J. Rogers" <dba_at_hjrdba.com> wrote in message news:afii1n$pj4$1_at_lust.ihug.co.nz...
> Altering a users quota to zero after they've created tables is a perfectly
> valid (though slightly unusual) thing to do, so I think you've got a
point,
> sort of.
>
> I'd agree with you that you might consider it a problem, except that it's
> dead easy to fix it: you just re-set the user's quota in the new database,
> and run import again for that particular schema. You then re-re-set the
> quota when all is finished. Fiddly, perhaps. But not terminal.
>
> I think, fundamentally, it's an issue of perception as to what import
does.
> All it does, in fact, is to read a bunch of 'create table' and 'insert
into'
> statements from the dump file. It's therefore dumb, and can't be expected
to
> finesse things by inventing commands which aren't in the dump file -that
> really would be a bug if it did!

Actuallty it does a little more than that. If you log on as a DBA and try to grant permissions on someone elses tables, you can't do it. Run a full import as that same DBA user and you can. Import behaves this way because if it didn't you would never be able to use it to completely restore a database. Received on Fri Jun 28 2002 - 16:07:38 CDT