[wp-hackers] Unsigned wp_posts.post_parent
philip at hetjens.eu
Thu Oct 15 07:01:28 UTC 2009
Yes, my plan was to change the scheme locally, but I wanted to avoid that
this change is revoked or that it creates problems when I update WP again.
2009/10/14 Brian Layman <Brian at b5media.com>
> Yeah, this has caused a whole lot of problems across b5 too. Basically any
> WP user with a plugin that worked with the post attachements/galleries had
> it break. In our case, we simply altered all of our databases restoring the
> signed field type. That got us into production immediately.
> We'd looked at possibly rewriting the code to look for 0 instead of -1,
> however upon further investication, that produced result sets of tens of
> thousands of items that had to be iterated, rather than the few posts that
> filtering -1 returned.
> I've not yet returned to this topic, but my next plan of attack was to
> create a constant for (essentially) max(unsigned bigint(20)) which is
> "18,446,744,073,709,551,615" according to http://bit.ly/VXYdk. I think we
> are safe to assume that there are no blogs with over a quintillion posts.
> Replacing that value in the plugins should be easy enough. Creating a
> constant for it - if there isn't one already, might not be a bad idea
> specifically for this kind of use.
> In anycase, either of these approaches might work for you, at least until
> the ticket is addressed.
> Brian Layman
> b5media, Inc.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
D-47608 Geldern (Germany)
Tel: +49 (0) 2838 / 91 00 6 - 5
Mobil: +49 (0) 171 / 69 17 501
Fax: +49 (0) 2838 / 91 00 6 - 6
Tel: +41 (0) 78 / 7 44 2 99 6
More information about the wp-hackers