1: Use 2 accounts. 1 for inserting/verifying, 1 for viewing. The applications that insert and validate, you give and account with permission to insert/Update. The application used for viewing you give an account with only select permission.
2: Use a checksum table.
create a table and a FK Constraint to the main table. The second table contains 1 field that is an md5 checksum of the value you are trying to protect. The only account that has insert access to the checksum table is the one that verifies the data. Once verified, it inserts a record into the checksum table. *Nobody should have delete or update permission to the checksum table!*
THEN your application that reads the data, also reads the checksum. It uses it to verify the data is unchanged.
Depending on the structure of your application and the resources available, you could put the checksum table on a separate server. This would isolate it even further and make it harder to crack.
Let me know how I may be of service, =C= * Cal Evans * http://www.eicc.com * We take care of your IT, * So you can take care of your business. * * I think inside the sphere.
Andre MATOS wrote:
Hi List,
Is anybody knows how to lock (make just readable) a field from a record or the whole record?
This is the idea: I need to create a table that some people will insert records. One person will access a record to validate the values inserted into it. Once a field was validated, nobody else can change the value again. The people can still look it, but just look.
If it is not possible to make readable the fields, is it possible the whole record?
Is this possible to do in MySQL? If it is, how can I do it and which version of MySQL should I use?
Thanks.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
