Hi Keikki,

   I would like to know if row level privileges can be set in mysql. 

  Eg:- 

   In user table, the user shall be allowed to edit only his record.

   In a table for task report, only assignee of the task shall be
allowed to edit the specific record.


-- Prabhu

On Thu, 27 Dec 2001, Heikki Tuuri wrote:

> Date: Thu, 27 Dec 2001 18:56:03 +0200
> From: Heikki Tuuri <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: InnoDB in MySQL-4.0.1
> 
> Hi!
> 
> InnoDB is a table type which provides transactions, row level locking, and
> foreign key constraints to MySQL.
> 
> InnoDB is included in all versions of MySQL-4.0 and in MySQL-Max-3.23.
> 
> The InnoDB version in the 4.0 series is identical to the version in the
> stable MySQL-Max-3.23 series. Therefore I list below the changes from
> MySQL-3.23.46. The changelog from 4.0.0 is much longer, and it is best to
> look at it from http://www.innodb.com/ibman.html
> 
> 
> * InnoDB allows now several similar key values in a UNIQUE secondary index
> if those values contain SQL NULLs. Thus the convention is now the same as in
> MyISAM tables.
> 
> * InnoDB gives a better row count estimate for a table which contains BLOBs.
> 
> * In a FOREIGN KEY constraint InnoDB is now case-insensitive to column
> names, and in Windows also to table names.
> 
> * InnoDB allows a FOREIGN KEY column of CHAR type to refer to a column of
> VARCHAR type, and vice versa. MySQL silently changes the type of some
> columns between CHAR and VARCHAR, and these silent changes do not hinder
> FOREIGN KEY declaration any more.
> 
> * Recovery has been made more resilient to corruption of log files.
> 
> * Unnecessary statistics calculation has been removed from queries which
> generate a temporary table. Some ORDER BY and DISTINCT queries will now run
> much faster.
> 
> * MySQL now knows that the table scan of an InnoDB table is done through the
> primary key. This will save a sort in some ORDER BY queries.
> 
> * The maximum key length of InnoDB tables is again restricted to 500 bytes.
> The MySQL interpreter is not able to handle longer keys.
> 
> Best regards and a Happy New Year!
> 
> Heikki Tuuri
> Innobase Oy
> [EMAIL PROTECTED]
> http://www.innodb.com
> 
> 
> 
> 
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> 

-----------------------------------------------------------
 Beauty is bought by judgement of the eye. 
                                -- Shakespeare
-----------------------------------------------------------
Prabhu SR.
Sankhya Technologies Private Limited, Chennai-34.
-----------------------------------------------------------


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to