Re: Error Connecting to MySQL DB 4.8.1.1

Resending as requested. Just as an update. I identified the cause for my computer locking up. Turns out to be a KDE Desktop wallpaper component I had enabled and not KMM. I have continued to use 4.8.1.1 since I have not been able to get 5.0 to compile on my box. I am still seeing the 6 per

Re: Error Connecting to MySQL DB 4.8.1.1

Just as an update. I identified the cause for my computer locking up. Turns out to be a KDE Desktop wallpaper component I had enabled and not KMM. I have continued to use 4.8.1.1 since I have not been able to get 5.0 to compile on my box. I am still seeing the 6 per manual entry insert/update via

Re: Error Connecting to MySQL DB 4.8.1.1

Tony, good to see signs of you. In case you want to tackle this, don't go with tarballs. You should use a clone from the (Git) repository and then switch to the right branch. For you to start this would be git clone git://anongit.kde.org/kmymoney.git which will create a subdir called

Re: Error Connecting to MySQL DB 4.8.1.1

The problem with the keyword 'order' is that, although it has been escaped, the character used is a double-quote. By default, Mysql doesn't recognize this; it expects a backtick as the escape character.  If you have access to the Mysql configuration, this can be fixed by the addition of the line

Re: Error Connecting to MySQL DB 4.8.1.1

As the original developer of the DB interface, I'm interested in this thread. I had a similar problem to the OP when I tried 4.8 under Windows, but when I tried looking a bit at the code, I found it had changed so much since I was last involved, and unfortunately didn't have much time available to

Re: Error Connecting to MySQL DB 4.8.1.1

It appears it finished processing my entries. I was able to start up the application and it logged in and loaded my database. First off, thanks for adding the Tags feature as adding the tags in memo was not the best way to search and group transactions. The one thing I have noticed is that it's

Re: Error Connecting to MySQL DB 4.8.1.1

I was able to use KMM 4.8.1.1 for about 4hr before my box became unresponsive. I don't know if it was due to a memory leak or something else. Nothing showed in the output and I was not really paying attention to what top was reporting regarding memory usage, I was focusing on cpu usage. During the

Re: Error Connecting to MySQL DB 4.8.1.1

So after running for 11 hours my box became unresponsive. I could move the mouse and the cursor reflected the move but that was all I could do. I tried to SSH and I got a response to the connect attempt but never got prompted for password (which would make sense seeing how I could only use the

Re: Error Connecting to MySQL DB 4.8.1.1

On Sonntag, 25. Februar 2018 04:51:18 CET El Cas wrote: > On Sun, Feb 25, 2018 at 2:31 AM, Thomas Baumgart wrote: > > Having the DB on a separate server should not make a difference. All > > communication (incl. structure updates etc) between KMyMoney and the SQL > > DB is >

Re: Error Connecting to MySQL DB 4.8.1.1

On Sun, Feb 25, 2018 at 2:31 AM, Thomas Baumgart wrote: > Having the DB on a separate server should not make a difference. All > communication (incl. structure updates etc) between KMyMoney and the SQL > DB is > via a communication link. > > I am not sure, if bringing in 5.0

Re: Error Connecting to MySQL DB 4.8.1.1

Hi, On Sonntag, 25. Februar 2018 06:53:18 CET El Cas wrote: > I have the DB on a separate server so that might be the reason why it did > not get upgraded. I am trying to login using Kubuntu 18.04 (2/24/18 Daily > Image) and KMM 5.0 and I am now getting a permission denied error when I > try to

Re: Error Connecting to MySQL DB 4.8.1.1

I have the DB on a separate server so that might be the reason why it did not get upgraded. I am trying to login using Kubuntu 18.04 (2/24/18 Daily Image) and KMM 5.0 and I am now getting a permission denied error when I try to login with the correct password. I will create a new test DB and

Re: Error Connecting to MySQL DB 4.8.1.1

Hi, this sounds very strange. Obviously, one of the upgrade steps regarding the DB backend failed along the way (I am by far no expert at that point and it is a guess to some extent). Another wild guess is, that the cause could be some missing columns in your DB that are now used. I would

Error Connecting to MySQL DB 4.8.1.1

I upgraded from Kubuntu 16.04 to 17.10. When I installed the 4.8.0 version that came with 17.10 and tried to connect to the DB where kmm 4.6.6 was storing my information I got the following error. *Query error no 1064: you have an error in your sql syntax; check the manual that corresponds to