gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] query result


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] query result
Date: Fri, 13 Dec 2013 10:33:21 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Fri, Dec 13, 2013 at 10:21:19AM +0100, Karsten Hilbert wrote:

> > >> Nevertheless I have eventually been able to identify the
> > >> problem: Apparently Vaibhav never ran any of the fixup
> > >> scripts against his v18 database. I don't know whether
> > >> an easy means to do so has been provided on Windows. The
> > >> 18 -> v19 upgrade does, however, run all v18 fixups
> > >> against the v18-state database just in case. That way
> > >> one more document template sneaked in which would have
> > >> been added with previous v18 fixups already.
> > 
> > I am afraid I do not understand.
> > 
> > If
> > 
> >     the 18 -> v19 upgrade "does, however, run all v18 fixups"
> > 
> > then what is the difference between whether or not any of the 18 fixups had 
> > been run (or not) if running the v19 upgrade would run the fixups.
> > 
> > IOW … why is it believed that the answer to
> > 
> >     So you are saying that running the fix-up scripts before
> >     upgrading would make the check work ?
> > 
> > is
> > 
> >     Yes.
> > 
> > when running the v18 --> 19 upgrade did not fix it?
> 
> The sanity checks are run against the original v18 and the
> newly created v19

That is to mean "the newly created, completely upgraded, v19".

> while the fixup scripts are running against
> the cloned-to-become-v19-but-still-v18 database before running
> the upgrade scripts against the cloned database.
> 
> Karsten
> -- 
> GPG key ID E4071346 @ gpg-keyserver.de
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
> 
> _______________________________________________
> Gnumed-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnumed-devel

-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

[Prev in Thread] Current Thread [Next in Thread]