How to distinguish between node and delete node in database?
first why i must do this?
I have tried most of the paging solutions in forum, performance is very low in the case of large amount of data, especially use of XSLT paging, test data 100 000 nodes, LoadRunner 100 concurrent time-consuming for a few minutes, almost collapsed, so I try to direct get paging data from the database, but get the deleted data, because umbraco delete nodes only mark the parentid -20, associated child nodes parentid unchanged, can not distinguish whether a node has been deleted, how do I use sql get undelete and released data rather than using the API or XSLT?
Well you must the internals and I think you must write a JOIN Query regarding some other tables to achieve what you want. The best way would be to check the umbraco source code and the write your own store procedure with paging. But you must then also adjust the database permissions for your account.
What approach do you currently use that has the low performance? Are you using the cached XML variant?
How to distinguish between node and delete node in database?
first why i must do this?
I have tried most of the paging solutions in forum, performance is very low in the case of large amount of data, especially use of XSLT paging, test data 100 000 nodes, LoadRunner 100 concurrent time-consuming for a few minutes, almost collapsed, so I try to direct get paging data from the database, but get the deleted data, because umbraco delete nodes only mark the parentid -20, associated child nodes parentid unchanged, can not distinguish whether a node has been deleted, how do I use sql get undelete and released data rather than using the API or XSLT?
my umbraco ver is 4.11.7
thanks in advance
can anybody help me?
Well you must the internals and I think you must write a JOIN Query regarding some other tables to achieve what you want. The best way would be to check the umbraco source code and the write your own store procedure with paging. But you must then also adjust the database permissions for your account.
What approach do you currently use that has the low performance? Are you using the cached XML variant?
if test nodes more than 50000, Takes about one minute to get results, I don't know why is slowly , can you tell me the best paging solution?
thanks Andreas Iseli
Hello,
Did you try the same thing with the new IPublishedContent? http://our.umbraco.org/documentation/Reference/Mvc/querying Maybe it's faster.
Jeroen
is working on a reply...