Re: [Gnumed-devel] psql upgrade

[Sebastian Hilbert]

Am Montag, 25. November 2013, 12:16:47 schrieb Karsten Hilbert:
> On Mon, Nov 25, 2013 at 12:01:38PM +0100, Hilbert, Sebastian wrote:
> > > > Fremdschl?ssel-Constraints:
> > > ...
> > > 
> > > >     "substance_intake_fk_encounter_fkey" FOREIGN KEY (fk_encounter)
> > > >     REFERENCES clin.encounter(pk) ON UPDATE CASCADE ON DELETE RESTRICT
> > > >     "substance_intake_fk_episode_fkey" FOREIGN KEY (fk_episode)
> > > >     REFERENCES clin.episode(pk) ON UPDATE CASCADE ON DELETE RESTRICT
> > > 
> > > Those two are lacking from Vaibhav's database.
> > 
> > Is it feasible to add these in a v18 database even now ? If I understand
> > this correctly the upgrade from v18 to v19 would add these but I guess
> > they are valid in a v18 production system as well ?
> 
> Sure enough. In fact, I don't remember when I added
> that check to the bootstrapper ... lemme check ...
> 
> Here's the commit:
> 
>       commit 69e6bfd29d04ec6c629eb5a11758ffa6283752ad
>       Author: Karsten Hilbert <address@hidden>
>       Date:   Fri Aug 2 12:27:38 2013 +0200
> 
> which corresponds to
> 
>       18.8
> 
>       FIX: ensure FKs on .fk_encounter/.fk_episode on clin.clin_root_item
> children
> 
> IOW, the bootstrapper already does those checks even
> under 1.3/v18. If people had run the database fixup
> scripts as they were advised to in the the release
> announcement they would already have those FKs set
> properly.
> 
> The fixup can be run now, too.
> 
> Karsten

I am certain he did not run the fixup scripts as I have not provided those for 
Windows explicetly. Will go check.

Sebastian