[wpmu-trac] [WordPress MU Trac] #1095: 2.8 sets ID fields to be unsigned; breaks functions dependent on inserting then querying for rows with ID -1

[WordPress MU Trac]

#1095: 2.8 sets ID fields to be unsigned; breaks functions dependent on inserting
then querying for rows with ID -1
----------------------------+-----------------------------------------------
 Reporter:  leenewton       |       Owner:  somebody                         
     Type:  defect          |      Status:  new                              
 Priority:  normal          |   Milestone:  2.8.2                            
Component:  Administration  |     Version:  2.8.2                            
 Severity:  normal          |    Keywords:  schema upgrade unsigned int ID -1
----------------------------+-----------------------------------------------
 Not much to add here, I've been debugging an issue with our sites where
 xmlrpc post inserts were no longer associating images with posts properly.

 The default behaviour is for an xmlrpc editor to upload a file which is
 intended to be inserted into the db with an ID of -1, then insert the post
 content, then query for attachments with an ID of -1 which have a guid
 that matches with the post content.

 Said query does not succeed because the post_parent can't be set to -1
 when inserted into the unsigned int. I imagine this has potentially far
 reaching repercussions within the rest of the code.

 I plan on undoing those field attribute changes but want to first check
 there's no current purpose for the change other than future proofing the
 tables a little bit.

 Cheers,
 Lee Newton

-- 
Ticket URL: <http://trac.mu.wordpress.org/ticket/1095>
WordPress MU Trac <http://mu.wordpress.org/>
WordPress Multiuser