[Kmymoney-devel] [Bug 249762] Kmymoney+mysql

[martin welsh]

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





--- Comment #2 from martin welsh <martin mhwelsh force9 co uk>  2010-09-02 17:17:33 ---
On 02/09/10 14:35, Fernando Vilas wrote:
> https://bugs.kde.org/show_bug.cgi?id=249762
>
>
>
>
>
> --- Comment #1 from Fernando Vilas<fvilas iname com>   2010-09-02 15:35:36 ---
> By "Mysql database beleived to be in place", do you mean that you did a "save
> as database" from an existing .kmy file?
>
> The line where it is failing is on a call to MyMoneyStorageSql::writeFileInfo.
> It never gets there, though.
>
>    
The bug report was instigated by repeat crashes.
A database |K|MyMoney was created and permissions were granted to the 
kmymoney user outwith the Kmymoney programme.
The kmymoney file was then downloaded to the database and I deduce that 
this happened by the progress line displayed at the bottom of the screen 
after the command
was issued.
When you reload the KMymoney programme you are presented with a form so 
that you can recall the data.  If I enter my password (the only entry 
left active) and press the go button the bug is produced.

"mysql KMyMoney -u kmymoney user -p
show tables:"

produces;
> +---------------------------+
> | Tables_in_KMyMoney        |
> +---------------------------+
> | kmmAccounts               |
> | kmmBalances               |
> | kmmBudgetConfig           |
> | kmmCurrencies             |
> | kmmFileInfo               |
> | kmmInstitutions           |
> | kmmKeyValuePairs          |
> | kmmPayees                 |
> | kmmPrices                 |
> | kmmReportConfig           |
> | kmmSchedulePaymentHistory |
> | kmmSchedules              |
> | kmmSecurities             |
> | kmmSplits                 |
> | kmmTransactions           |
> +---------------------------+
> 15 rows in set (0.00 sec)

I hope that helps.

ps what is the mysql command that shows the table contents?

martin welsh

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.