Android Question MySql, PHP, B4A wait for query to finish

[Oscarin]

I am using this tutorial

Connect Android to MySQL Database Tutorial

A new more powerful framework is now available: jRDC2. This tutorial explains the basic concepts required for creating a connection between Android device and a remote server. In this case it is a MySQL database. A tutorial for connecting to SQL Server is available here. Android cannot connect...

www.b4x.com

To connect to a MySQL DB, everything works fine, but I have a problem.
Sometimes I need for the query to finish before proceeding to the next line of code
This is what I want to do
I do a SELECT * FROM and base on the result I give a variable a TRUE or FALSE value and will do either an INSERT or an UPDATE, the problem is that because is asynchronous
the value never changes, I don't want to use the sleep function because I don't know how much time it will take for the result to be given, and I know that I can use the WAIT FOR but unfortunately I don't know where to put it and how to use it.
Any help would be appreciated.

PS
I am using the same code as the tutorial, just modified to my needs.

 

[Erel]

I am using this tutorial

Most probably a mistake.

About Wait For: [B4X] OkHttpUtils2 with Wait For

 

[DonManfred]

Most probably a mistake.

This is a second thread about the same Issue.

Wait for, need help on how to use it

Hi, I am using this tutorial on how to connect to MySQL DB https://www.b4x.com/android/forum/threads/connect-android-to-mysql-database-tutorial.8339/ But I have a problem because I need to wait for the query to finish before proceeding on to the next process. I send a SELECT * FROM and I need to...

www.b4x.com

 

[Oscarin]

Most probably a mistake.

About Wait For: [B4X] OkHttpUtils2 with Wait For

Thanks for the reply.

Can you elaborate a little more on what do you mean bi mistake?
Thanks

 

[Oscarin]

This is a second thread about the same Issue.

Wait for, need help on how to use it

Hi, I am using this tutorial on how to connect to MySQL DB https://www.b4x.com/android/forum/threads/connect-android-to-mysql-database-tutorial.8339/ But I have a problem because I need to wait for the query to finish before proceeding on to the next process. I send a SELECT * FROM and I need to...

www.b4x.com

Yes, sorry about that, the thing is that I searched for this (my first post) and I was not able to find it

 

[Erel]

Can you elaborate a little more on what do you mean bi mistake?

The PHP based solution is insecure, less powerful and slower than jRDC2.

 

[Oscarin]

The PHP based solution is insecure, less powerful and slower than jRDC2.

Sorry to bother again, but insecure in what way?
We already have some projects in html/php running in our servers, that is why I don't want to load another piece of software just to run some small tasks

 

[Erel]

It is explained in the tutorial: https://www.b4x.com/android/forum/threads/connect-android-to-mysql-database-tutorial.8339/
A malicious client can send arbitrary SQL commands to the server. You must be careful to set the correct privileges.

This cannot happen with with jRDC2 as the commands are set on the server side.

 

[Oscarin]

It is explained in the tutorial: https://www.b4x.com/android/forum/threads/connect-android-to-mysql-database-tutorial.8339/
A malicious client can send arbitrary SQL commands to the server. You must be careful to set the correct privileges.

This cannot happen with with jRDC2 as the commands are set on the server side.

Got it.
Thank you for the explanation.

 

[KMatle]

Of course php is NOT insecure but you can't just call a DB function without adding security. Mostly it's not just calling some db functions from an app. There's more. And this is the strength of PHP (or any other server client). You can check if a request is valid/allowed (via user credentials/message signing, encryption, etc.). You can do enything with it.

Mostly apps directly calling db functions are not safe enough and not accepted by customers/security/regulation authorities, etc.

 

[Andrew (Digitwell)]

Of course php is NOT insecure but you can't just call a DB function without adding security. Mostly it's not just calling some db functions from an app. There's more. And this is the strength of PHP (or any other server client). You can check if a request is valid/allowed (via user credentials/message signing, encryption, etc.). You can do enything with it.

Mostly apps directly calling db functions are not safe enough and not accepted by customers/security/regulation authorities, etc.

I would also agree with this. I used to roll my own PHP code to access remote databases, but now have switched to Laravel in PHP on the server side. Much easier to be sure that it is secure and as @kmantle says much more accepted by customers etc.

This may seem like overkill if you just want to get/store a small bit of data so it is worth considering your use case. SLIMPHP is also another option.

 

[aeric]

One of the issue is SQL injection. Imagine a client send something like SELECT * FROM tbl_user WHERE admin = 1 or DELETE * FROM tbl_Products. The client also can read some users sensitive data like password and query all the database schemas if database user privileged not set correctly.

There are many more secure ways like web services or web API. If you have a VPS, JRDC2 is a better solution.

 

[Erel]

I was referring to that specific example.