[kmymoney] [Bug 390979] securities have changed into currency

[Thomas Baumgart]

https://bugs.kde.org/show_bug.cgi?id=390979

Thomas Baumgart  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kmy
   ||money/6e2321172a285f686e7d7
   ||95577fce23702bfc672
 Resolution|--- |FIXED

--- Comment #2 from Thomas Baumgart  ---
Git commit 6e2321172a285f686e7d795577fce23702bfc672 by Thomas Baumgart.
Committed on 24/02/2018 at 16:58.
Pushed by tbaumgart into branch 'master'.

Fix security retrieval from engine

The call to MyMoneyFile::currency() not only returns currencies but also
securities. This was broken due to a recent change.

M  +13   -4kmymoney/mymoney/mymoneyfile.cpp

https://commits.kde.org/kmymoney/6e2321172a285f686e7d795577fce23702bfc672

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 390979] securities have changed into currency

[David Nelson]

https://bugs.kde.org/show_bug.cgi?id=390979

--- Comment #3 from David Nelson  ---
this looks good now.
thanks for the speedy fix!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 390967] quantity in Investments view should be right-justified

[Thomas Baumgart]

https://bugs.kde.org/show_bug.cgi?id=390967

Thomas Baumgart  changed:

   What|Removed |Added

   Version Fixed In||5.0.1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmymoney] [Bug 390979] securities have changed into currency

[Thomas Baumgart]

https://bugs.kde.org/show_bug.cgi?id=390979

Thomas Baumgart  changed:

   What|Removed |Added

   Priority|NOR |HI
   Severity|normal  |grave
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Thomas Baumgart  ---
This seems to be the requested follow-up to #390044. I keep the reference here,
as it contains a specific commit (5.0.80-7150b4a5) that might be related to the
problem.

In fact, this might be a problem on current git master which changes your data
(I have seen the same here in my data and cannot experience the problem in the
5.0 branch).

So it is very likely that master is currently broken in the investment storage
area. Here's what I have done. I opened a file written with 5.0 (where
investments are shown correctly) in master and I see, that the file is modified
without me doing anything. Saving the file and comparing it shows the following
effect (besides others which are not causing trouble):

in the file written by 5.0 I see:



and the same record in the file written by master shows as



The order of the attributes is not a problem, but the modification of the
currency attribute is causing the trouble and explains what the OP sees.

The file contents must be fixed manually (reverting the currency assignment)
and master is currently broken for that. I adjusted the importance of this
entry accordingly.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Error Connecting to MySQL DB 4.8.1.1

[El Cas]

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 your mysql server version for the right syntax
to use near '"order" smallint unsigned not null, identifier varchar(32) not
null, primary k' at line 1 qmysql: unable to execute query.*

I noticed that there was a 4.8.1 version so I added the repo for that
version and uninstalled 4.8.0 and installed 4.8.1. I then got a cannot open
shared library libkmm_settings.so file missing error.

I uninstalled 4.8.1 and proceed to to download the source code and I fired
off the build for tag 4.8.1.1 using the provided instructions in
README.cmake and it all compiled correctly but when I ran it I got the
following error.

*Cannot open file as requested. Error was: Error in function void
MyMoneyStorageSql::writeFileInfo() : writing FileInfo*

*Driver = QMYSQL, Host = X.X.X.X, User = kmymoney, Database = kmymoney*

*Driver Error: *

*Database Error No -1: *

*Text: *

*Error type 0*

*Executed: UPDATE kmmFileInfo SET version = ?, fixLevel = ?, created = ?,
lastModified = ?, baseCurrency = ?, dateRangeStart = ?, dateRangeEnd = ?,
hiInstitutionId = ?, hiPayeeId = ?, hiTagId = ?, hiAccountId = ?,
hiTransactionId = ?, hiScheduleId = ?, hiSecurityId = ?, hiReportId = ?,
hiBudgetId = ?, hiOnlineJobId = ?, hiPayeeIdentifierId = ?, encryptData =
?, updateInProgress = ?, logonUser = ?, logonAt = ?, institutions = ?,
accounts = ?, payees = ?, tags = ?, transactions = ?, splits = ?,
securities = ?, prices = ?, currencies = ?, schedules = ?, reports = ?,
kvps = ?, budgets = ?; *

*Query error No -1: *

*Error type 0*

Is there something I can do to (besides reverting back to Kubuntu 16.04/KMM
4.6.6) to resolve this issue?

Re: Error Connecting to MySQL DB 4.8.1.1

[Thomas Baumgart]

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 suggest to make a backup of your DB (that's a good 
idea in any case), create a new empty database and compare the table 
structures (using external SQL tools). I expect a difference to show up 
somewhere. Then it would be a matter to correct the difference.

@all: in case anyone has a better idea, please speak up. The OP is not 
subscribed to the list, so please CC him.

Hope that helps as a first step. If you have further questions, please let us 
know. Make sure to send answers to the list and not to individuals only.

Regards

Thomas


On Samstag, 24. Februar 2018 21:16:21 CET El Cas wrote:

> 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 your mysql server version for the right syntax
> to use near '"order" smallint unsigned not null, identifier varchar(32) not
> null, primary k' at line 1 qmysql: unable to execute query.*
> 
> I noticed that there was a 4.8.1 version so I added the repo for that
> version and uninstalled 4.8.0 and installed 4.8.1. I then got a cannot open
> shared library libkmm_settings.so file missing error.
> 
> I uninstalled 4.8.1 and proceed to to download the source code and I fired
> off the build for tag 4.8.1.1 using the provided instructions in
> README.cmake and it all compiled correctly but when I ran it I got the
> following error.
> 
> *Cannot open file as requested. Error was: Error in function void
> MyMoneyStorageSql::writeFileInfo() : writing FileInfo*
> 
> *Driver = QMYSQL, Host = X.X.X.X, User = kmymoney, Database = kmymoney*
> 
> *Driver Error: *
> 
> *Database Error No -1: *
> 
> *Text: *
> 
> *Error type 0*
> 
> *Executed: UPDATE kmmFileInfo SET version = ?, fixLevel = ?, created = ?,
> lastModified = ?, baseCurrency = ?, dateRangeStart = ?, dateRangeEnd = ?,
> hiInstitutionId = ?, hiPayeeId = ?, hiTagId = ?, hiAccountId = ?,
> hiTransactionId = ?, hiScheduleId = ?, hiSecurityId = ?, hiReportId = ?,
> hiBudgetId = ?, hiOnlineJobId = ?, hiPayeeIdentifierId = ?, encryptData =
> ?, updateInProgress = ?, logonUser = ?, logonAt = ?, institutions = ?,
> accounts = ?, payees = ?, tags = ?, transactions = ?, splits = ?,
> securities = ?, prices = ?, currencies = ?, schedules = ?, reports = ?,
> kvps = ?, budgets = ?; *
> 
> *Query error No -1: *
> 
> *Error type 0*
> 
> Is there something I can do to (besides reverting back to Kubuntu 16.04/KMM
> 4.6.6) to resolve this issue?

-- 

Regards

Thomas Baumgart

https://www.telegram.org/   Telegram, the better WhatsApp
-
Of all the computing resources available, the most valuable one is
programmers' time. Especially in open source where most of us have to
sneak in time to write and debug code. (Ace Jones)
-


signature.asc
Description: This is a digitally signed message part.

Re: Error Connecting to MySQL DB 4.8.1.1

[El Cas]

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 compare the tables and see if I notice a
difference in table structure. I will report back to this email.

On Sun, Feb 25, 2018 at 6:46 AM, Thomas Baumgart  wrote:

> 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 suggest to make a backup of your DB (that's a
> good
> idea in any case), create a new empty database and compare the table
> structures (using external SQL tools). I expect a difference to show up
> somewhere. Then it would be a matter to correct the difference.
>
> @all: in case anyone has a better idea, please speak up. The OP is not
> subscribed to the list, so please CC him.
>
> Hope that helps as a first step. If you have further questions, please let
> us
> know. Make sure to send answers to the list and not to individuals only.
>
> Regards
>
> Thomas
>
>
> On Samstag, 24. Februar 2018 21:16:21 CET El Cas wrote:
>
> > 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 your mysql server version for the right syntax
> > to use near '"order" smallint unsigned not null, identifier varchar(32)
> not
> > null, primary k' at line 1 qmysql: unable to execute query.*
> >
> > I noticed that there was a 4.8.1 version so I added the repo for that
> > version and uninstalled 4.8.0 and installed 4.8.1. I then got a cannot
> open
> > shared library libkmm_settings.so file missing error.
> >
> > I uninstalled 4.8.1 and proceed to to download the source code and I
> fired
> > off the build for tag 4.8.1.1 using the provided instructions in
> > README.cmake and it all compiled correctly but when I ran it I got the
> > following error.
> >
> > *Cannot open file as requested. Error was: Error in function void
> > MyMoneyStorageSql::writeFileInfo() : writing FileInfo*
> >
> > *Driver = QMYSQL, Host = X.X.X.X, User = kmymoney, Database = kmymoney*
> >
> > *Driver Error: *
> >
> > *Database Error No -1: *
> >
> > *Text: *
> >
> > *Error type 0*
> >
> > *Executed: UPDATE kmmFileInfo SET version = ?, fixLevel = ?, created = ?,
> > lastModified = ?, baseCurrency = ?, dateRangeStart = ?, dateRangeEnd = ?,
> > hiInstitutionId = ?, hiPayeeId = ?, hiTagId = ?, hiAccountId = ?,
> > hiTransactionId = ?, hiScheduleId = ?, hiSecurityId = ?, hiReportId = ?,
> > hiBudgetId = ?, hiOnlineJobId = ?, hiPayeeIdentifierId = ?, encryptData =
> > ?, updateInProgress = ?, logonUser = ?, logonAt = ?, institutions = ?,
> > accounts = ?, payees = ?, tags = ?, transactions = ?, splits = ?,
> > securities = ?, prices = ?, currencies = ?, schedules = ?, reports = ?,
> > kvps = ?, budgets = ?; *
> >
> > *Query error No -1: *
> >
> > *Error type 0*
> >
> > Is there something I can do to (besides reverting back to Kubuntu
> 16.04/KMM
> > 4.6.6) to resolve this issue?
>
> --
>
> Regards
>
> Thomas Baumgart
>
> https://www.telegram.org/   Telegram, the better WhatsApp
> -
> Of all the computing resources available, the most valuable one is
> programmers' time. Especially in open source where most of us have to
> sneak in time to write and debug code. (Ace Jones)
> -
>