[GeoNode-devel] DB migrations

Emanuele Tajariol etj at geo-solutions.it
Fri Jun 3 10:20:30 PDT 2016


Hi list,

I created a pull request for geonode for the db migration issue:

   https://github.com/GeoNode/geonode/pull/2490

Since the deps with other modules are quite intertwined, I also had to create 
migrations for other repos, as explained in 

   https://github.com/GeoNode/geonode/issues/2488

namely:
-    geonode_dialogos-0.4
-    geonode_agon_ratings-0.3.4
-    geonode_user_accounts-1.0.10
-    geonode_avatar-2.1.4
-    geonode_announcements-1.0.7
-    geonode_user_messages-0.1.2

I guess that the version numbers of these apps should be bumped up (along with 
the deps in geonode as well), but I don't know if these repos' version numbers 
follow the ones of the originally forked projects, or if they are proceeding 
on their own. Anyway you may know better than me how to handle this.

After all of these changes will be applied, running a 

    python manage.py migrate

will properly create from scratch a valid geonode db.


   Cheers,
   Emanuele


Alle 12:43:47 di Wednesday 1 June 2016, Simone Dalmasso ha scritto:
> Yes we used south. But the migrations squash is new to me and looks a cool
> feature.
> 
> 2016-06-01 10:57 GMT+02:00 Emanuele Tajariol <etj at geo-solutions.it>:
> > Hi Simone,
> > 
> > for each release we could as well provide the unique migration script by
> > making django squash the single migrations created while developing the
> > new release, as documented in
> > 
> >    https://docs.djangoproject.com/en/1.8/topics/migrations/#squashing-
> > 
> > migrations
> > 
> > I thought this was quite a new feature in geonode since migrations have
> > been
> > introduced in django 1.7 as far I can see. Did you use South?
> > 
> >    Cheers,
> >    Emanuele
> > 
> > Alle 10:27:57 di Wednesday 1 June 2016, Simone Dalmasso ha scritto:
> > > We used to have migrations in the past but then dropped them in favor
> > > of
> > 
> > a
> > 
> > > unique migration script between stable versions. This because there
> > > were
> > 
> > so
> > 
> > > many changes that most of the migrations were actually useless and
> > 
> > messing
> > 
> > > up the procedure. I'm +0
> > > 
> > > Il mercoledì 1 giugno 2016, Alessio Fabiani <
> > > 
> > > alessio.fabiani at geo-solutions.it> ha scritto:
> > > > +1
> > > > 
> > > > Best Regards,
> > > > Alessio Fabiani.
> > > > 
> > > > ==
> > > > GeoServer Professional Services from the experts!
> > > > Visit http://goo.gl/it488V for more information.
> > > > ==
> > > > 
> > > > Ing. Alessio Fabiani
> > > > @alfa7691
> > > > Founder/Technical Lead
> > > > 
> > > > GeoSolutions S.A.S.
> > > > Via di Montramito 3/A
> > > > 55054  Massarosa (LU)
> > > > Italy
> > > > phone: +39 0584 962313
> > > > fax:     +39 0584 1660272
> > > > mob:   +39 331 6233686
> > > > 
> > > > http://www.geo-solutions.it
> > > > http://twitter.com/geosolutions_it
> > > > 
> > > > -------------------------------------------------------
> > > > 
> > > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
> > > > 
> > > > Le informazioni contenute in questo messaggio di posta elettronica
> > > > e/o nel/i file/s allegato/i sono da considerarsi strettamente
> > > > riservate. Il loro utilizzo è consentito esclusivamente al
> > > > destinatario del
> > 
> > messaggio,
> > 
> > > > per le finalità indicate nel messaggio stesso. Qualora riceviate
> > > > questo messaggio senza esserne il destinatario, Vi preghiamo
> > > > cortesemente di darcene notizia via e-mail e di procedere alla
> > > > distruzione del
> > 
> > messaggio
> > 
> > > > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio
> > 
> > stesso,
> > 
> > > > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo,
> > > > od utilizzarlo per finalità diverse, costituisce comportamento
> > > > contrario
> > 
> > ai
> > 
> > > > principi dettati dal D.Lgs. 196/2003.
> > > > 
> > > > 
> > > > 
> > > > The information in this message and/or attachments, is intended
> > > > solely for the attention and use of the named addressee(s) and may
> > > > be confidential or proprietary in nature or covered by the
> > > > provisions of privacy act (Legislative Decree June, 30 2003, no.196
> > > > - Italy's New
> > 
> > Data
> > 
> > > > Protection Code).Any use not in accord with its purpose, any
> > 
> > disclosure,
> > 
> > > > reproduction, copying, distribution, or either dissemination, either
> > > > whole or partial, is strictly forbidden except previous formal
> > > > approval of the named
> > > > addressee(s). If you are not the intended recipient, please contact
> > > > immediately the sender by telephone, fax or e-mail and delete the
> > > > information in this message that has been received in error. The
> > > > sender does not give any warranty or accept liability as the
> > > > content, accuracy or completeness of sent messages and accepts no
> > > > responsibility  for changes made after they were sent or for other
> > > > risks which arise as a result of e-mail transmission, viruses, etc.
> > > > 
> > > > ---------------------------------------------------------------------
> > > > 
> > > > On Wed, Jun 1, 2016 at 10:21 AM, Emanuele Tajariol <
> > 
> > etj at geo-solutions.it
> > 
> > > > <javascript:_e(%7B%7D,'cvml','etj at geo-solutions.it');>> wrote:
> > > >> Hi List,
> > > >> 
> > > >> in order to have django properly update the db schema when some
> > 
> > changes
> > 
> > > >> in the
> > > >> models are performed, it needs some initial migration files, as
> > > >> described in
> > > >> 
> > > >>     https://docs.djangoproject.com/en/1.8/topics/migrations/.
> > > >> 
> > > >> This change may still be related to the porting to django 1.8.
> > > >> 
> > > >> I can provide a PR for this.
> > > >> 
> > > >>    Cheers,
> > > >>    Emanuele
> > > >> 
> > > >> --
> > > >> ==
> > > >> GeoServer Professional Services from the experts!
> > > >> Visit http://goo.gl/NWWaa2 for more information.
> > > >> ==
> > > >> 
> > > >> Ing. Emanuele Tajariol
> > > >> Technical Lead
> > > >> 
> > > >> GeoSolutions S.A.S.
> > > >> Via di Montramito 3/A
> > > >> 55054  Massarosa (LU)
> > > >> Italy
> > > >> phone: +39 0584 962313
> > > >> fax:    +39 0584 1660272
> > > >> mob:   +39 380 2116282
> > > >> 
> > > >> http://www.geo-solutions.it
> > > >> http://twitter.com/geosolutions_it
> > > >> 
> > > >> -------------------------------------------------------
> > > >> _______________________________________________
> > > >> geonode-devel mailing list
> > > >> geonode-devel at lists.osgeo.org
> > > >> <javascript:_e(%7B%7D,'cvml','geonode-devel at lists.osgeo.org');>
> > > >> http://lists.osgeo.org/mailman/listinfo/geonode-devel
> > 
> > --
> > ==
> > GeoServer Professional Services from the experts!
> > Visit http://goo.gl/NWWaa2 for more information.
> > ==
> > 
> > Ing. Emanuele Tajariol
> > Technical Lead
> > 
> > GeoSolutions S.A.S.
> > Via di Montramito 3/A
> > 55054  Massarosa (LU)
> > Italy
> > phone: +39 0584 962313
> > fax:    +39 0584 1660272
> > mob:   +39 380 2116282
> > 
> > http://www.geo-solutions.it
> > http://twitter.com/geosolutions_it
> > 
> > -------------------------------------------------------


-- 
==
GeoServer Professional Services from the experts! 
Visit http://goo.gl/NWWaa2 for more information.
==

Ing. Emanuele Tajariol
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:    +39 0584 1660272
mob:   +39  380 2116282 

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------


More information about the geonode-devel mailing list