You've been perfectly clear. The MySQL permission system will not define this level of security. You must design you application so that it will only give access to the rows that pertain to the customer that is logged in. Create a MySQL user which can read and write to your database. Then create another table in your database which defines users and passwords (separate from the MySQL users). When a user logs in, you check their username and password against your user table, and then once they are logged in, you make sure the only rows they see or update are rows that pertain to them.
I hope this makes things clear. On Wednesday 10 March 2004 05:39 pm, Mulugeta Maru wrote: > Hi Mike, > > I am sorry for the confusion I might have caused. May be it would help to > give a clear example. > > Table - Customers (CustomerID, CustomerName, Address, etc) > > Table - Transaction(TransactionID,CustomerID,Date,Amount) > > Note: CustomerID in Customer Table is a Primary Key. TransactionID is a > Primary Key and CustomerID is a Foreign Key in Transaction Table). > > Question: How would I be able to give my customers access to the database > so that they can update the customer table (for example address change) and > add transactions to the transaction table. What I do not want to happen is > that customer A is able to modify customer B's record. > In short how would you restrict customer a to see transactions that pertain > to him/her. > > Many thanks. -- Joshua J. Kugler Fairbanks, Alaska Computer Consultant--Systems Designer .--- --- ... .... ..- .- -.- ..- --. .-.. . .-. [EMAIL PROTECTED] ICQ#:13706295 Every knee shall bow, and every tongue confess, in heaven, on earth, and under the earth, that Jesus Christ is LORD -- Count on it! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
