Thanks Arjen,
seems like a bit of a fiddle but not a bad solution considering some of the
other options. Unfortunately I also need the row level locking of innodb
so it's not going to work in my case. This lead me to ponder, if this
sort of row level protection was added would it be at the
Hi Noel,
On Tue, 2002-02-19 at 13:40, [EMAIL PROTECTED] wrote:
> I'm wondering about row level privilages - being able to restrict what
> people see and can update etc on a row level as well as a column/table
> level.
As others mentioned, having VIEWs wouldn't necessarily be of any help,
since
On Tue, 2002-02-19 at 00:46, Gregory Junker wrote:
> For reasons of the end-arounds you note it really has to be in the
> server. As mentioned views are a possibility, but could end up being
> just as messy as a middle tier. It sounds like what you want is
> integrated (with the OS) security (as i
t I'm sure it could be done in a future version. :)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 18, 2002 10:40 PM
> To: [EMAIL PROTECTED]
> Subject: row level privilages - thoughts on how to do
>
>
>
On Mon, 2002-02-18 at 21:40, [EMAIL PROTECTED] wrote:
> I'm wondering about row level privilages - being able to restrict what
> people see and can update etc on a row level as well as a column/table
> level.
> So, anyone got any ideas about how you'd best go about this? Will
> triggers/ stor
Hi all,
I'm wondering about row level privilages - being able to restrict what
people see and can update etc on a row level as well as a column/table
level.
I know that I can implement it in my program (which is what I'm currently
doing) but unless it's in the backend db then every program tha
