Re: hot to limit sqlldr ?
From: Stefan <stefan_at_dragolov.com>
Date: 13 Apr 2005 07:27:13 -0700
Message-ID: <1113402433.811868.295760_at_f14g2000cwb.googlegroups.com>
Date: 13 Apr 2005 07:27:13 -0700
Message-ID: <1113402433.811868.295760_at_f14g2000cwb.googlegroups.com>
[Quoted] [Quoted] ideally you are correct - however, I am hosting an application which
[Quoted] [Quoted] requires that the application level user have the same username and
password as the database level user, AND the database level user has to
have insert/update/delete in order to be able to use the application's
front end....
I know it's a horrible design, but that's the way it is....
so the only thing I've been able to think of so far is to create a LOGON trigger which kills sessions unless they are made via the appropriate client application...
was wondering if there are any other ideas out there... Received on Wed Apr 13 2005 - 16:27:13 CEST