[07:08] good morning [08:22] Morning o/ === ejat_ is now known as ejat [15:02] dpm: call? :) [15:08] ok, looks like it's not happening [15:09] dholbach, sorry, I updated the calendar, but I meant to ping you [15:09] leaving a bit earlier today to catch a flight [15:09] ok [15:09] dholbach, let's catch up tomorrow [15:10] dpm, mhall119, davidcalle: short update: I think I'm close to having the importer fixed [15:10] dholbach, wow, nice way to finish the year! :-) [15:10] yes [15:11] dholbach: wow, how? [15:11] because publishing etc will change a pages PK [15:11] Page().publish() creates a new copy of the page (and deletes the old one) [15:11] (PK = primary key) [15:12] I'm using cms.api.publish_pages([list]) now and modified a few lookups [15:12] I'm still testing things though :) [15:12] dholbach: so, publishing in bulk as opposed to page by page? [15:12] yes [15:13] we often passed page objects around, for example to set the parent of a new article [15:13] dholbach: this raises a lot of questions about why Django does things differently for each case and why mysql doesn't care [15:14] if we do a .publish() in between it might break things or have bizarre effects [15:14] it could be that sqlite reuses PKs and postgres doesn't - it was one of ojii's first assumptions this morning [15:14] In any case, we don't *need* an answer for these, I'm just so very glad you found a way :D [15:15] I'll make sure to add more tests, just in case :) [16:57] all right my friends - I call it a day - see you tomorrow!