Has the database schema changed?

[S McGraw]

On 04/03/2016 09:58 AM, Colin Law wrote:
> On 3 April 2016 at 16:23, John Ralls <jralls at ceridwen.us> wrote:
>>> On Apr 3, 2016, at 7:59 AM, Colin Law <clanlaw at gmail.com> wrote 
>>> Has the database schema changed recently?  I have some scripts
>>> that extract reports from the mysql db and the prices table
>>> appears to be empty.  I cannot immediately find where they have
>>> moved to.  To save me wading through everything can anyone help
>>> me out?  I am now on 2.6.9, I think I was on 2.6.3 before.
>> 
>> No schema changes, but a change in the way currency exchange rates
>> are handled. This has been discussed at length here over the last
>> several months. If you're querying currency exchange rates try
>> reversing the exchange-rate direction. BTW, the change was
>> introduced in 2.6.9 and naturally produced a few bugs. All of the
>> reported ones have been fixed in 2.6.12 so I suggest that you
>> upgrade to that if you're doing multi-currency transactions.
> 
> Thanks John. I do recall those discussions but I don't do any 
> multicurrency which is why they did not trigger warning bells for
> me. It appears the problems also apply in some cases to
> non-multicurrency situations.  However that is all water under the
> bridge.  It may be a bit of an issue for Ubuntu however as the 16.04
> release is past feature freeze which means that unfortunately it is
> stuck with 2.6.9, for the moment anyway.
> 
> It is also a bit of a problem for me as getdeb have not released a
> deb for Ubuntu 16.04 yet, but that is the sort of problem you expect
> to face if running with a pre-release version of the OS.  I will try
> the latest deb for 15.10, it will likely be ok.  Otherwise I will
> have to drag out my notes on building from source :)
> 
> Thanks again Colin

Just as confirmation, I too ran into the same problem without any 
multicurrency transactions involved, albeit with Postgresql rather
than MySQL, as described in:

  http://lists.gnucash.org/pipermail/gnucash-user/2015-November/062613.html

In my case downgrading back to 2.6.7 fixed the problem until I was 
able to upgrade my OS (fedora) and get 2.6.11.