Native Development

[simon_hain]

I am referring to the "Quotes" sample app on https://github.com/blackberry/Cascades-Samples/tree/master/quotes

There a SqlDataAccess object is created and execute() is called.

After that QSqlDatabase::addDatabase is called to create a "non default connection".

Do I have to do that as well? Or could i just work with the SqlDataAccess object? If yes, what would be the up/downsides for that?

[simon_hain]

It seems i can answer my question, working with SqlDataAccess seems to work fine, i only had to ensure the creation of the database with QFile.

I can write my values into the database, but i have some problems reading them, as i don't fully comprehend the QVariant return value.

I execute a sql statement that returns "2" (I use SQLite Database browser to test).

QVariant result = sqlDataAccess->execute("SELECT...)

How do i extract the result from the QVariant?

All the samples throw the whole thing into a listview (or use a different mechanism to query the db).

And how would i do it for a more complex result?

[gperry]

http://qt-project.org/doc/qt-4.8/qvariant.html

Should give you the information you require - whole point of QVariant is that you can define it how you want using toInt, toString etc. QVariant can be used to store any type of data using the value/setValue functions.

Regards

Graham

[simon_hain]

Hi Graham,

i am aware of than. But the debugger seems to be unable to tell me what is in the object, and when i call toint() on a QVariant that should contain the value '2' i get 0.

My problem is that i don't really know what the return value stored in QVariant is.

[rcmaniac25]

Not really an expert in this, haven't had a need to work with QVariant. Have you tried calling {qvar}.type() to determine that it is indeed an int?

[simon_hain · Accepted solution]

I got the solution to that on the BB Jam from one of the Cascades developers, did not manage to update this post until now.

You can use qDebug() << qVariant to check what exactly is in the QVariant.
RIM also promised to update the API docs to include more advanced usecases in the sample.