https://bugs.kde.org/show_bug.cgi?id=371331
--- Comment #6 from Simeon Kuran <simeon.ku...@gmail.com> ---
No, I don't think so!
Most of the time, the error occurs far before executing the SQL SELECT
statement!
I have to admit, that it's hard to debug, because sometimes all works as it
should. I needed several attempts too, but then I got the following error on
console:
"using database failed: KDbResult: OK"
When executing the following piece of code:
bool cancelled;
bool ok = m_connection->useDatabase(database, KEXI_COMPATIBLE, &cancelled);
if (ok)
{
qDebug() << "using DB '" << database << "'." << endl;
emit databaseAvailable(database);
}
else
{
qDebug() << "using database failed: " << m_connection->result();
}
In Kexi the situation is much worse: Opening a project only works by a chance
of 1 to 5 or so... (the other 4 times it fails with different error messages).
I am quite sure this is because Kexi of course fires much more PostgreSql / DB
commands and one or the other just fails.
Shall I add my Kexi binaries to the git repo too? Maybe it would be interesting
whether you can see the described effects too with it? .... Though I know that
I didn't set up KReport correctly, but at the moment I don't need it and I am
sure it doesn't affect this error. In Kexi such DB errors show up quite
frequently when I create a new project, add some simple tables, store the
project and then try to reopen it.
I know this comment sounds a bit like if my incomplete setup of Kexi causes the
error, but I am quite sure that's not the case. I am very convinced, that the
error happens in KDb (at least in my self compiled KDb version. I don't want to
blame KDb for it though. I can not / and don't want to exclude, that I simply
did something wrong! )
Thanks for your efforts!
--
You are receiving this mail because:
You are watching all bug changes.
