[wp-trac] Re: [WordPress Trac] #3418: Issues with importing/converting blogroll from 2.0.5

[WordPress Trac]

#3418: Issues with importing/converting blogroll from 2.0.5
--------------------------+-------------------------------------------------
 Reporter:  Viper007Bond  |        Owner:  anonymous
     Type:  defect        |       Status:  new      
 Priority:  high          |    Milestone:  2.1      
Component:  General       |      Version:  2.1      
 Severity:  normal        |   Resolution:           
 Keywords:                |  
--------------------------+-------------------------------------------------
Comment (by BrianLayman):

 I'm a little concerned about the merging code in this area...

 Ok, so basicaly, because of the code in admin-db.category_exists, the
 first category wins.  However, since no "order by" clause is specified in
 that query, we aren't going to know for sure which the "first" category is
 going to be. At least that's how it would work in a relational DB.  The
 order of the results would be dependant upon the order in which the data
 was inserted and when it was modified last.  So the order could be by ID
 or it could be by when the user inserted it or if they did a restore it
 could be the order by which the restore inserted the records.

 Additionally, the Category_exists function doesn't cast the stuff to a
 specific case when checking for an existing name.  So we could end up with
 WordPress and Wordpress categories (as an example) because of how the
 blogger first typed them in in Posts vs links. I don't know if that's a
 design choice, or design oversight.  Either way could be argued for I
 suppose, but there are no comments in the code indicating whether this
 issue was considered.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3418#comment:4>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software