<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear Devs,<div class=""><br class=""></div><div class="">I´d like to share some experiences migrating geonode database (not geonode_data!) </div><div class="">from 2.4 to 2.8. This is what I did:</div><div class=""><br class=""></div><div class="">1) _<span class="Apple-tab-span" style="white-space:pre"> </span>dumped geonode 2.4 database</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>$ sudo -u postgres -i pg_dump -c -Fc geonode > /some_path/geonodedb.backup</div><div class=""><br class=""></div><div class="">2) _<span class="Apple-tab-span" style="white-space:pre"> </span>installed fresh geonode 2.8 (Ubuntu with project)</div><div class="">3) _ <span class="Apple-tab-span" style="white-space:pre"> </span>created new DB imported old 2.4 dump</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>$ sudo -u postgres createdb -O geonode geonode_new;</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>$ sudo -u postgres -i pg_restore -Fc -d geonode_new /some_path/geonodedb.backup</div><div class=""><br class=""></div><div class="">4) _ <span class="Apple-tab-span" style="white-space:pre"> </span>run migrations</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>$ python manage.py migrate --fake-initial --settings=my_geonode.local_settings</div><div class=""><br class=""></div><div class="">this ended in several problems like </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>people_timezone field was expected but did not exist. </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>layers_layer.service_id already existed.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">After some rubber duck debugging it worked the moment I´ve deleted layers_layer.service_id</div><div class="">before migration:</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>$ sudo -u postgres psql -d geonode_new -c 'ALTER TABLE "layers_layer" DROP COLUMN service_id‘</div><div class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>$ python manage.py migrate --fake-initial --settings=my_geonode.local_settings</div></div><div class=""><br class=""></div><div class="">Good to know: </div><div class=""><div class="">===========</div></div><div class="">It worked no matter if I´ve used a dump from 2.4 directly or by doing a intermediate migration by use</div><div class="">of geonode 2.6! In every case I´ve ended with 99 tables.</div><div class=""><br class=""></div><div class="">Conclusion:</div><div class="">=========</div><div class="">I´ve just tested with demo data installed by paver by now but suspect a bug with migration from</div><div class="">layers: 0029_layer_service.py. </div><div class=""><br class=""></div><div class="">My vage ques is that layers_layer.service_id is created by a previous running migration from service app. </div><div class="">The only workaround I´ve found so far is by backup and delete mentioned field (—fake brought new problems). </div><div class=""><br class=""></div><div class="">I hope this helps others, if somebody has a better solution how to solve this issue I´m open year !</div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">Toni</div><div class=""><br class=""></div><div class="">@Francesco: this time the moon was on my side ;D</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="">-----------------------------------------------</div><div class="">CSGIS</div><div class=""><br class=""></div><div class="">-----------------------------------------------</div><div class=""><div class="" style="orphans: 2; widows: 2;">Kolonnadenstraße 1</div><div class="" style="orphans: 2; widows: 2;">04109 Leipzig</div></div><div class="">-----------------------------------------------</div><div class="">Mobil<span class="Apple-tab-span" style="white-space: pre;"> </span>+49/ (0) 176 6680 3198</div><div class="">Tel <span class="Apple-tab-span" style="white-space: pre;"> </span>+49/ (0) 341 24 04 738</div><div class="">Fax <span class="Apple-tab-span" style="white-space: pre;"> </span>+49/ (0) 341 24 04 73</div><div class="">Web<span class="Apple-tab-span" style="white-space: pre;"> </span><a href="http://csgis.de" class="">http://csgis.de</a></div><div class="">-----------------------------------------------</div><div class=""><br class=""></div><div class="">Hinweis gemäß § 33 BDSG</div><div class="">Daten der Verfahrensbeteiligten werden gespeichert. Dieses Dokument ist ausschließlich für den </div><div class="">Adressaten bestimmt. Der Inhalt der E-Mail ist vertraulich. Falls Sie diese E-Mail versehentlich </div><div class="">erhalten haben, rufen Sie uns unter obiger Rufnummer umgehend an und löschen Sie diese Nachricht </div><div class="">von Ihrem Computer. Jegliche Art von Reproduktionen, Verbreitung, Vervielfältigung, Veränderung, </div><div class="">Verteilung und/oder Veröffentlichung dieser E-Mail ist verboten.</div></div></div></div></div></div></div></div>
</div>
<br class=""></div></body></html>