I would guess that the limit you are hitting is related to the "path" property on the UmbracoNode table. This has a character length of 150 chars, which assuming node ID's (which start from 1000 generally) are still only 4 digits long would give you potentially 30 nodes (as each node id is seperated by a ,. But if any node ID is greater than 4 chars (which is quite likely) it would reduce this limit.
On another note... can I ask why you are doing this? This level of nesting would raise red flags with me and I'd want to know if the content can be restructured.
I have already fixed this issue by making the limit to nvarchar(MAX).But is their any reason for limiting this path ?yes i am able to restructure the node?
Does it cause any other issue?
Is their any Child Node Limit?
Is their a limit to the number of children a single node can have ? eg Node1 -->Node 1.1 -->Node 1.1.1 -->Node 1.1.1.1.
Getting an error while publishing the 25th one.
"String or binary data would be truncated. The statement has been terminated."
Hi Nevin,
I would guess that the limit you are hitting is related to the "path" property on the UmbracoNode table. This has a character length of 150 chars, which assuming node ID's (which start from 1000 generally) are still only 4 digits long would give you potentially 30 nodes (as each node id is seperated by a
,. But if any node ID is greater than 4 chars (which is quite likely) it would reduce this limit.Thanks
Nik
On another note... can I ask why you are doing this? This level of nesting would raise red flags with me and I'd want to know if the content can be restructured.
I second this. Going to an extend of 25 node levels seems bizzare !
I have already fixed this issue by making the limit to nvarchar(MAX).But is their any reason for limiting this path ?yes i am able to restructure the node? Does it cause any other issue?
is working on a reply...