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