Bug 343108 - The 'memo' field in the 'kmmTransactions' table is not updated for duplicated transactions
Summary: The 'memo' field in the 'kmmTransactions' table is not updated for duplicated...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: database (show other bugs)
Version: 4.7.1
Platform: MacPorts macOS
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-21 04:30 UTC by Guy Germeaux
Modified: 2022-11-16 05:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guy Germeaux 2015-01-21 04:30:05 UTC
When duplicating a transaction and changing the memo of any leg of that transaction, the 'memo' field in the 'kmmSplits' table is updated to the new text, but the 'memo' field in the 'kmmTransactions' table always keeps its original value.

Reproducible: Always

Steps to Reproduce:
1. Select an existing transaction.
2. Duplicate the selected transaction.
3. Edit the memo field of the duplicated transaction.
4. Check the contents of the SQLite database (memo field in kmmTransactions and kmmSplits).

Actual Results:  
The memo field in kmmSplits contains the new value.
The memo field in kmmTransactions contains still the original value.

Expected Results:  
The memo field in kmmSplits contains the new value.
The memo field in kmmTransactions contains also the new value.

I am using kMyMoney4 with an SQLite3 database on OS X 10.10.1.
Comment 1 Justin Zobel 2022-10-17 00:40:52 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 2 Guy Germeaux 2022-10-17 04:45:10 UTC
Hello Justin,

I am currently not working with the latest version, so I will have to countercheck.

In previous versions, the reported error was easily reproducible (just choosing “duplicate” for an existing transaction and the memo field was always blank).

Regards,
Guy


> On 17 Oct 2022, at 02:40, Justin Zobel <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=343108
> 
> Justin Zobel <justin.zobel@gmail.com> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|REPORTED                    |NEEDSINFO
>         Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #1 from Justin Zobel <justin.zobel@gmail.com> ---
> Thank you for reporting this bug in KDE software. As it has been a while since
> this issue was reported, can we please ask you to see if you can reproduce the
> issue with a recent software version?
> 
> If you can reproduce the issue, please change the status to "CONFIRMED" when
> replying. Thank you!
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 3 Jack 2022-10-17 15:25:55 UTC
This actually sounds like correct behavior to me.  Perhaps something has changed since this bug was filed, but changing the memo of a split should not change the memo of the transaction.  
First, I want to be sure that the problem is not present immediately after duplicating a transaction, but only after editing it.  Then, are you saying that the behavior is different in an original transaction and a duplicate?  Please try again, as I think you will find the same behavior in the original transaction.
Finally, the back end should not matter here, unless what you see stored in the database (after saving) does not match what was shown in the ledger before (or after) saving.  Can you confirm whether the problem appears in the ledger before you save the data, or only after.
Comment 4 Bug Janitor Service 2022-11-01 05:05:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-11-16 05:16:46 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!