Sorry, I was wrong. It is an issue of our app.
On 1/24/2022 11:40 AM, Alexander Dyagilev wrote:
Hello,
Let's suppose we have a database file of 16GB in size.
We open it using this code:
m_db = QSqlDatabase::addDatabase(
"QSQLITE",
dbConnectionName());
On Monday, 24 January 2022 02:41:38 PST Alexander Dyagilev wrote:
> Sorry, I don't really know (and I do not even care). But this is what
> Windows Task Manager shows to our users, and they are concerned about this.
Easy way to answer this: try to open a database that is bigger than the
virtual
On 1/24/2022 12:39 PM, Hamish Moffatt via Interest wrote:
Did you mean to misspell journal_mode?
LOL. OK, fine... ROFL... No, of course no...
Are you sure it's real memory usage and not just address space used by
mmap?
Sorry, I don't really know (and I do not even care). But this is what
On Mon, Jan 24, 2022 at 11:40 AM Hamish Moffatt via Interest
wrote:
>
> On 24/1/22 19:40, Alexander Dyagilev wrote:
> > Hello,
> >
> > Let's suppose we have a database file of 16GB in size.
> >
> > We open it using this code:
> >
> > m_db = QSqlDatabase::addDatabase(
> > "QSQLITE",
>
On 24/1/22 19:40, Alexander Dyagilev wrote:
Hello,
Let's suppose we have a database file of 16GB in size.
We open it using this code:
m_db = QSqlDatabase::addDatabase(
"QSQLITE",
dbConnectionName());
m_db.setConnectOptions("PRAGMA jounal_mode=WAL;");
Hello,
Let's suppose we have a database file of 16GB in size.
We open it using this code:
m_db = QSqlDatabase::addDatabase(
"QSQLITE",
dbConnectionName());
m_db.setConnectOptions("PRAGMA jounal_mode=WAL;");
m_db.setDatabaseName(m_dbPath);
m_db.open();
After this, our
