[ASK] Using MySQL UDF, how to make it safe?

[michaelslamet]

In my AutoIT app, I would like to allow user to edit values of a MySQL database through a GUI Interface,

but since this database is accessed (read and write) by many users at the same time and this is a very important database,

I afraid my AutoIT application damage the database when write to it without any prevention.

I mean what it's going to happen if my app write to the database while some other users open the record

and in a edit mode through their own interface/GUI ? What if my app and the user write the database on the

same time? and other scenario that I cant think at this moment?

If it dangerous, I will only display the value through my app and display a message to ask the user to

edit the value manually through their own interface/GUI.

If this important to tell: the user's gui is created using visual foxpro and access to the mysql through ODBC.

I hope somebody understand what I mean :-D

Merry Christmas and Happy New Year, everybody

[water]

You tell the database what you want to do (read, edit) and then it's the job of the database to make sure that only one session changes a record at the same time (that's called a transaction).

Check the MySQL documentation how to savely code what you need.

[michaelslamet]

Hi Water,

So I only need to tell the database what to do (read/edit) through MySQL UDF and the mysql server will take care the rest including the safety?

[water]

Correct. This is what databases are for.

Before you start to work with databases (MySQL in your case) you need some basic understanding how databases work. Get a good book or internet tutorial and don't start to code before you know how it works.

Use a test database before releasing your script to production.

Just my 2 cents.

[michaelslamet]

Ok, thanks a lot, Water

[water]