How to retrieve results from mysql_info() function

[rioba]

In MySQL, after a LOAD DATA INFILE statement I would like to run a

Code: Select all

mysql_info()

function to get information on the records inserted, skipped, and so on. How can I do this inside Servoy? Thanks for your help

[lvostinar]

In MySQL, after a LOAD DATA INFILE statement I would like to run a

Code: Select all

mysql_info()

function to get information on the records inserted, skipped, and so on. How can I do this inside Servoy? Thanks for your help

Use raw sql plugin ?

[rioba]

Yes, I thought of that, but I don't know how to extract the information. The Servoy function returns a boolean, and I normally use raw sql plugin to manipulate the db but not to get back information inside Servoy. That's the problem.

[lvostinar]

Yes, I thought of that, but I don't know how to extract the information. The Servoy function returns a boolean, and I normally use raw sql plugin to manipulate the db but not to get back information inside Servoy. That's the problem.

Can't you use a stored procedure to retrieve that information ?

[rioba]

Thank you for your tip. I have done a lot of tests using a stored procedure as you suggested, but with no success. Either I am doing something wrong or maybe a MySQL C API function such as mysql_info() doesn't work inside a stored procedure. Some time ago I had a similar problem not being able to show inside Servoy the warnings generated by a MySQL statement and I could not solve it using straight SQL functions or statements. But i don't remember the workaround, if any, I used then.

[lvostinar]

Thank you for your tip. I have done a lot of tests using a stored procedure as you suggested, but with no success. Either I am doing something wrong or maybe a MySQL C API function such as mysql_info() doesn't work inside a stored procedure. Some time ago I had a similar problem not being able to show inside Servoy the warnings generated by a MySQL statement and I could not solve it using straight SQL functions or statements. But i don't remember the workaround, if any, I used then.

You could open a case/feature request so that we can investigate how to solve this.