Skip to main content
replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/
Source Link

I understand that post ID's are uniquepost ID's are unique, but are they reliable as persistent data ID's?

More specifically, is there a guarantee that, through a migration or another data exchange, post ID's will not change?

I understand wordpress is primarily implemented using MySQL, so ID's are governed by the AUTO_INCREMENT mechanism; however, is there any caveat on Wordpress' end that would change this behavior in the future, or potentially with another persistence implementation (such as MongoDB)?

I understand that post ID's are unique, but are they reliable as persistent data ID's?

More specifically, is there a guarantee that, through a migration or another data exchange, post ID's will not change?

I understand wordpress is primarily implemented using MySQL, so ID's are governed by the AUTO_INCREMENT mechanism; however, is there any caveat on Wordpress' end that would change this behavior in the future, or potentially with another persistence implementation (such as MongoDB)?

I understand that post ID's are unique, but are they reliable as persistent data ID's?

More specifically, is there a guarantee that, through a migration or another data exchange, post ID's will not change?

I understand wordpress is primarily implemented using MySQL, so ID's are governed by the AUTO_INCREMENT mechanism; however, is there any caveat on Wordpress' end that would change this behavior in the future, or potentially with another persistence implementation (such as MongoDB)?

Tweeted twitter.com/#!/StackWordPress/status/519609073252044800
Source Link

Are post ID's reliable?

I understand that post ID's are unique, but are they reliable as persistent data ID's?

More specifically, is there a guarantee that, through a migration or another data exchange, post ID's will not change?

I understand wordpress is primarily implemented using MySQL, so ID's are governed by the AUTO_INCREMENT mechanism; however, is there any caveat on Wordpress' end that would change this behavior in the future, or potentially with another persistence implementation (such as MongoDB)?