database error

[jsulm]

@fkaraokur said in database error:

"db.db"

This is relative path and you wrote that it is in your project folder. But your app is looking in its current working directory which is the build folder by default, so it can't find it. Deploy the database file to the build folder. Use https://doc.qt.io/qt-5/qstandardpaths.html if you deploy your application to find the database file. Also if you need to write that file you should put it in a writable location.

[Bonnie]

@JonB You're right.
Quoted from the doc:

For the QSQLITE driver, if the database name specified does not exist, then it will create the file for you unless the QSQLITE_OPEN_READONLY option is set.

[fkaraokur]

@jsulm said in database error:

@fkaraokur said in database error:

"db.db"

This is relative path and you wrote that it is in your project folder. But your app is looking in its current working directory which is the build folder by default, so it can't find it. Deploy the database file to the build folder. Use https://doc.qt.io/qt-5/qstandardpaths.html if you deploy your application to find the database file. Also if you need to write that file you should put it in a writable location.

When I put the db.db file in the compilation folder, it will run, right? So which is this folder? Isn't it correct if I specify the folder where the database file is located like this?

 QString path = "D:/Qt_Project/BIST/db.db";
    QSqlDatabase db;
    db = QSqlDatabase::addDatabase("QSQLITE");
    db.setDatabaseName(path);

[JonB]

@fkaraokur
The "compilation folder" is purely an artefact of, well, compiling :) It does not have any runtime equivalent. In itself you'd have to hard-code that.

But this is not the right place anyway to put a database which will be accessible at runtime, when your code is distributed. You probably want one of the "runtime user writeable" locations offered via the link @jsulm provided you with earlier.

If you are saying in your situation that D:/Qt_Project/BIST/db.db is where the file sits yet the code you show fails to find/open it, then something sounds wrong.

[Driftwood]

@fkaraokur - I'm not sure where you are with this, but I'll show you what works for me. From mainwidow.cpp

MainWindow::MainWindow(QWidget *parent) :
    QMainWindow(parent),
    ui(new Ui::MainWindow)
{
    ui->setupUi(this);

    swDB = QSqlDatabase::addDatabase("QSQLITE");
    QDir dbDir;
    dbDir.mkdir("db");
    swDB.setDatabaseName("db/data.db");

    if (!swDB.open())
        ui->statusBar->showMessage(swDB.lastError().text());
    else
    {
        /*
         * THE FOLLOWING ENSURES FOREIGN KEYS WILL BE ENABLED
         * FOR SQLITE3. THIS MUST BE THE FIRST QUERY EXECUTED
         * WHEN THE APP STARTS.
         */
        QSqlQuery q(swDB);
        q.exec("PRAGMA foreign_keys = 1");
        qDebug() << "Foreign Keys have been enabled";

        ui->statusBar->showMessage("Database connected");
    }
    swDB.close();
}

And in mainwindow.h put this:

private:
    QSqlDatabase swDB;

The code works flawlessly. However, if you're concerns are based on the database being created after you delete it, that's normal. If the db isn't present when you run your code, Qt creates it. Every time.

[SGaist]

@Driftwood said in database error:

@fkaraokur - I'm not sure where you are with this, but I'll show you what works for me. From mainwidow.cpp

MainWindow::MainWindow(QWidget *parent) :
    QMainWindow(parent),
    ui(new Ui::MainWindow)
{
    ui->setupUi(this);

    swDB = QSqlDatabase::addDatabase("QSQLITE");
    QDir dbDir;
    dbDir.mkdir("db");
    swDB.setDatabaseName("db/data.db");

    if (!swDB.open())
        ui->statusBar->showMessage(swDB.lastError().text());
    else
    {
        /*
         * THE FOLLOWING ENSURES FOREIGN KEYS WILL BE ENABLED
         * FOR SQLITE3. THIS MUST BE THE FIRST QUERY EXECUTED
         * WHEN THE APP STARTS.
         */
        QSqlQuery q(swDB);
        q.exec("PRAGMA foreign_keys = 1");
        qDebug() << "Foreign Keys have been enabled";

        ui->statusBar->showMessage("Database connected");
    }
    swDB.close();
}

And in mainwindow.h put this:

private:
    QSqlDatabase swDB;

The code works flawlessly. However, if you're concerns are based on the database being created after you delete it, that's normal. If the db isn't present when you run your code, Qt creates it. Every time.

As the QSqlDatabase documentation warns: it's highly not recommended to keep a QSqlDatabase class member.

[jsulm]

@fkaraokur said in database error:

So which is this folder?

If you're using QtCreator you can check in "Projects/General/Build directory".
"When I put the db.db file in the compilation folder, it will run, right?" - yes, it should.

"Isn't it correct if I specify the folder where the database file is located like this?" - of-course you can do this, but keep in mind that your app is then fixed to this location of the database file and you can only change that if you change the code and rebuild.

[Driftwood]

@SGaist said in database error:

As the QSqlDatabase documentation warns: it's highly not recommended to keep a QSqlDatabase class member.

That's what I get for learning from a youtube video and not reading. Thank you for showing me that.

[fkaraokur]

There was a folder right next to where I saved the project. I thought it would be the build folder and put the db file there. and it worked. I am using my database without any problems.

BIST  //I was putting the db file here but it was wrong
build-BIST-Desktop_Qt_5_15_1_MinGW_64_bit-Debug   //fixed here

[JonB]

@fkaraokur
I am lost as to where you are at now. Do you have some path working where it picks up an existing database as you desire, or is it still not finding any database and is creating a new one each time?

If you are saying it is working for you by putting the database into some directory like build-BIST-Desktop_Qt_5_15_1_MinGW_64_bit-Debug, you really should read what we have all said above. This is just not the right place to put a database file. For example, it won't work once you compile for Release, it won't exist if anybody but you runs the program, and if you did distribute your application read/writing a database in the same directory as the executable will at best be a bad idea and at worst be forbidden.