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.
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.
This has been fixed in the development version (1.1.5-alpha) where the p2p_type column has a length of 44 chars.
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?
Because a longer key means a bigger INDEX and/or slower queries.
Could you give an example of such a verbose naming convention?
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.
You must log in to post.