@Christian-Ehrlicher I solved the problem. After digging deeper, I found that in the function QMYSQLResult::reset(const QString& query) in the source code qsql_mysql.cpp, the field type of all data was set to the default value MYSQL_TYPE_DECIMAL(0). Also, I saw that it was loading another libmariadb.dll from the list of loaded dlls, which I had not specified. Eventually, I decided to start over, and after deleting Qt, MariaDB, MariaDB connector, and environment variables, rebuilding, installing, and building the plugin, it finally worked fine. I still don't know exactly what the problem was, but thank you for your attention.

@Christian-Ehrlicher said in QSql performance consideration/data flow design.:

Ok, I would never consider those functions as replacement for stored procedure.

I agree, but it is their documentation, I guess "Lite" means "lite" :)

@Christian-Ehrlicher Thanks!!

@swankster
:) Like I said, just build the (correct, including whatever quoting, and if you are OK on possible SQL injection attacks!) string and pass that without using binding, for this query.

@Narutoblaze
Then no you cannot, as you can see in the documentation for QTcpSocket/ QAbstractSocket. If there were a method which took a "connection name" you would see it documented.

There is nothing to stop you writing your own code to store connections indexed by some "connection name" you choose, e.g. using a QMap Class.

@Donald9307

Just to clear the confusion, do you have any model or in which way do you use your query?
Because there is no QSqlQuery::setQuery() (as in the title).

But good to hear that it worked for you :)

I have worked with the qsqlcipher plugins well and gone through with the qsqlcipher plugin code and I puted some print statement in the plugin code itself then observed that the fetchNext function taking is more time, Please look into it

@RyanSolanki Please mark as solved if you are happy the issue is resolved. Also consider reading up further about Qt's memory management model (maybe it would make sense to pass a parent during the QSqlQueryModel's construction to avoid all that manual memory management or else perhaps smart pointers if there is no clear parent to assign ownership to).

Furthermore, SGaist's point about passing a pointer to a function whose signature expects a const reference cannot be understated. If the function expects a pointer, give it a pointer. If it expects a const reference, give it an object created on the stack! https://doc.qt.io/qt-5/qsqlquerymodel.html#details
The documentation is good; use it! It is unclear to me why you are using functions such as "clear" for the model. The setQuery() function already clears the model. Why mess around with new and delete several times when you can just pass in a new query to modify the existing model? Futhermore, why bother clear()-ing the model immediately before you delete it? The destructor is called during the delete, which itself frees up any resources, per the documentation.

There are deeper problems of comprehension going on here!

Thx. Will take a look on it and hope it will go into 5.15 (even we as opensource user currently don't have an advantage currently but this hopefully changes somehow in the near future)

@Max13 said in Store custom QVariant type in database:

I will write a toJson() instead, as I'm loading the data from Json already.

Sounds good.

Thanks for your advice. Indeed, it would be the correct way to implement this, in my situation I didn't think it would be necessary to implement it that way.

I'm updating some models from an API, and save them as a read-only cache in an sqlite because the desktop may be disconnected. So in my opinion, adding another table would make me write more queries and deal with relations when I can do that in a nasty way 😅

That's fair enough. Simplicity is often a good thing in code.

Thanks for your complete answer.

You're most welcome. Happy coding!

Process still block, when I lost connection.

@Kent-Dorfman said in calling stored procedure with prepared query vs execute:

Since a stored procedure is simply a server-side wrapper around an SQL transaction, it is IRRELEVANT AND REDUNDANT to wrap it in a prepared statement on the client.

Yes, I start to understand what you mean.
I will study in deep this argument.

Thanks a lot for your precious comments.

@SGaist

My bad ! I did not think to check the docs on that point !

A big thanks
Gérard

@bartoszpaj said in BindValue() in QPSQL is not working?:

driver()->hasFeature(QSqlDriver::NamedPlaceholders) returns false.

Good catch. I think it's because support for PostgreSQL 10 was added in a later version. If the version is not known to the driver it will fall back to the oldest.

@SGaist I did it this way for reading return params:

Query.nextResult(); // after reading table values //Get Return Parameter for (int i=0; i<CountReturnParam; i++) { qDebug() << QString("Returnparam %1 = %2") .arg(i).arg(Query.boundValue(i).toString()); }

Hi,

There’s also no need to allocate the query on the heap as the QSqlQueryModel::setQuery method parameter suggests.

As it is now, double is used.

Depending on how your DECIMAL filed is configured, it might be enough. If not, then you can modify the plugin to read the field as described here.

@jsulm said in Cannot retrieve the SQL query string from QSqlQuery?:

@mostefa This is not the answer to the question as @JNBarchan want to have the query text not its result.
From your example he wants to get "SELECT id,name,birthday FROM artist".

@mostefa As @jsulm says, I am indeed not looking to execute the query, rather only to retrieve its text.
This has indeed turned out to be QSqlQuery::lastQuery(), and I have now marked this question as Solved. Thanks all.

hi,

@LuAria ,

wat ws the value coming in Numtwo ?.
Nways ur got solution.
Happy coding.

Thanks,

Hi,

Did you check that you are using similar connection parameters for both your Dephi and C++ application ?