LinkedIn
Twitter
Hello,
I have an App that it's connected to a MySQL database.
The way that the DB manager generates his keys for all his tables is through an integer column with auto increment.
I could try to calculate the next auto increment key value but I believe this will create conflics in the future (e.g. multiple users saving records at the same time).
However, I could be able to feed the column key through Appsheet, but we will have users also pouring information into the database through a web-app as well.
Under this scenario, is it possible for MySQL to generate a unique ID as Appsheet does?
If that is not possible, and the MySQL database must key the int + auto increment, shall we have two key columns? one used in the Appsheet environment and the other on the web-app environment?
Is there any other approach we could take?
Thanks in advance!
Solved
1 ACCEPTED SOLUTION
Please take a look at the following article and the section "Working with IDENTITY columns" .
https://help.appsheet.com/en/articles/962066-using-data-from-mysql#working-with-special-characters
The recommendation in the article is, please create a NVARCHAR (8) type column as key and assign it as a key column. In AppSheet editor, assign UNIQUEID() as initial value for this column. Please test well. An example from a test app below.
Edit: I had missed this part " but we will have users also pouring information into the database through a web-app as well." in your post. The reference article I shared is basically for recommended practice for key column in MYSQL DB connected to an AppSheet app. However the approach does not answer your requirement of "adding information in the DB through other app".
