#6032 (Remove SiteConfig.next_partner_id)

by Luc Saffre · in Developers · assigned to Luc Saffre

Summary

Because this was actually an nonsense-feature. The first Lino customer (weleup) wanted this, back in 2010. Meanwhile they also don't use it anymore. Nobody else has ever wanted such a feature. Technically spoken it doesn't handle race conditions correctly. And it disturbed for importing data from TIM.

Children

Comments

1 year, 6 months ago by Luc Saffre about #6032 (Remove SiteConfig.next_partner_id) : Uff! I pushed my changes in more than 10 repositories. I had to adapt the doctests in ca 100 files. One doctest is still failing because I can't explain it.
1 year, 6 months ago by Luc Saffre about #6032 (Remove SiteConfig.next_partner_id) : As expected, this is a bit of a monk's work because it caused all the partner ids to start at 1 instead of 100. There were 51 test failures in the book.
1 year, 6 months ago by Luc Saffre about #6032 (Remove SiteConfig.next_partner_id) : Created new Ticket #6032 (Remove SiteConfig.next_partner_id).