Title: [Plugin: Posts 2 Posts] Database column size issue
Last modified: August 20, 2016

---

# [Plugin: Posts 2 Posts] Database column size issue

 *  Resolved [jtwg](https://wordpress.org/support/users/jtwg/)
 * (@jtwg)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-posts-2-posts-database-column-size-issue/)
 * I use a script to programmatically create connections based on content type names.
   With the newest release, I’m now having errors because the size of the name field
   is only 32 characters.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [scribu](https://wordpress.org/support/users/scribu/)
 * (@scribu)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-posts-2-posts-database-column-size-issue/#post-2543877)
 * This has been fixed in the [development version](http://downloads.wordpress.org/plugin/posts-to-posts.zip)(
   1.1.5-alpha) where the p2p_type column has a length of 44 chars.
 *  Thread Starter [jtwg](https://wordpress.org/support/users/jtwg/)
 * (@jtwg)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-posts-2-posts-database-column-size-issue/#post-2544014)
 * It seems it should be much longer than 44 characters. If you have verbose naming
   conventions, 44 is still quite short. Why not make it something like 128?
 *  Plugin Author [scribu](https://wordpress.org/support/users/scribu/)
 * (@scribu)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-posts-2-posts-database-column-size-issue/#post-2544015)
 * Because a longer key means a bigger INDEX and/or slower queries.
 * Could you give an example of such a verbose naming convention?
 *  Thread Starter [jtwg](https://wordpress.org/support/users/jtwg/)
 * (@jtwg)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-posts-2-posts-database-column-size-issue/#post-2544016)
 * Good point. Didn’t think about the indexing.
 * Thanks for the response. I guess I will see if this winds up being an issue. 
   😉
 * On edit: interestingly, when I updated to 1.1.5, the column size remained at 
   32.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘[Plugin: Posts 2 Posts] Database column size issue’ is closed to new 
replies.

 * ![](https://s.w.org/plugins/geopattern-icon/posts-to-posts_7a8e9d.svg)
 * [Posts 2 Posts](https://wordpress.org/plugins/posts-to-posts/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/posts-to-posts/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/posts-to-posts/)
 * [Active Topics](https://wordpress.org/support/plugin/posts-to-posts/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/posts-to-posts/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/posts-to-posts/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [jtwg](https://wordpress.org/support/users/jtwg/)
 * Last activity: [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-posts-2-posts-database-column-size-issue/#post-2544016)
 * Status: resolved