[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #11 from Jack --- Not a problem. It's always hard to tell how much programming experience anyone has, but I figure sql is not a trivial thing to learn, so if you've gotten that far, you can probably figure out more :-) I'll leave it to

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread JAH
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #10 from JAH --- Well I'm very grateful for your consideration and raising the wish list entry. Sorry I misunderstood your point about the function. As a complete amateur I did try an extensive search for a solution / function but only came

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473322 Jack changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread JAH
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #8 from JAH --- >>"I'll see if it's reasonable to add a checkbox to toggle the use of the >>commas" - That would be great if possible because as you say, I don't believe they have any place in a numerical field. Surely it's more properly

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #7 from Jack --- No, given that description, I think the presence of the commas is intentional. I just didn't notice it. I'll see if it's reasonable to add a checkbox to toggle the use of the commas, but I'm not sure at this point. In

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread JAH
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #6 from JAH --- Thanks for your kind reply (and work on kmymoney). I use the sqlite3 command to process preprepared .sql queries that produce .csv reports with calculated ratios etc. I noticed that prices (over 1000) stored in the

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #5 from Jack --- The ONLY change I made was in the name of the variable being formatted. I don't believe thousand separators (commas) should ever be used in such variables. I'm not aware of any KMM setting that should have made them be

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-14 Thread JAH
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #4 from JAH --- Thanks so much for fixing this issue, it will make writing SQL queries so much easier! BTW am I right in thinking these ."valueFormatted" fields will no longer include comma thousand separators (which previously had to be

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-13 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473322 Jack changed: What|Removed |Added Version Fixed In||5.1.4 Latest Commit|

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-13 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #2 from Jack --- Git commit 6641cad7c940a0867fd106e14bebba00d51bdf4c by Jack Ostroff. Committed on 13/08/2023 at 19:25. Pushed by ostroffjh into branch 'master'. Fix sql sharesFormatted to use shares instead of price M +1-3

[kmymoney] [Bug 473322] SLQLite "kmmSplits"."sharesFormatted" Data Corrupt perhaps??

2023-08-12 Thread Jack
https://bugs.kde.org/show_bug.cgi?id=473322 --- Comment #1 from Jack --- Ouch. You are right, sharesFormatted does appear to be the price, formatted to a precision dependent on the account of the split. I'll have to dig into the code to see what's going on. -- You are receiving this mail