Comments on: Nested Set Trees in ColdFusion http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/ Sun, 08 Jan 2012 15:53:25 +0000 hourly 1 By: Kevan Stannard http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/comment-page-1/#comment-29 Kevan Stannard Fri, 22 May 2009 16:50:57 +0000 #comment-29 Hi Will Your plan sounds good to me. Let me know if you have any questions on getting up and running with the library. Regards Kevan Hi Will

Your plan sounds good to me.

Let me know if you have any questions on getting up and running with the library.

Regards

Kevan

]]> By: Will Tomlinson http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/comment-page-1/#comment-28 Will Tomlinson Fri, 22 May 2009 16:20:23 +0000 #comment-28 This category tool is perfect for what I need in my e-comm store application. I have a dumb question. I have a typical product table. productid as PK. I need a product to be related to one or more categories and/or subcategories, any level deep. Would I simply create a linking table between my products table and category table? And use categoryId as a FK in my linking table? That way a product can be related to one or more items in the category table. Thank you so much! Will This category tool is perfect for what I need in my e-comm store application.

I have a dumb question. I have a typical product table. productid as PK.

I need a product to be related to one or more categories and/or subcategories, any level deep.

Would I simply create a linking table between my products table and category table? And use categoryId as a FK in my linking table? That way a product can be related to one or more items in the category table.

Thank you so much!

Will

]]> By: Aaron Lee http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/comment-page-1/#comment-27 Aaron Lee Fri, 06 Jun 2008 17:08:13 +0000 #comment-27 Hi Kevan, That's great! I will certainly look forward to it. Hi Kevan,

That’s great! I will certainly look forward to it.

]]> By: Kevan Stannard http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/comment-page-1/#comment-26 Kevan Stannard Fri, 06 Jun 2008 14:22:15 +0000 #comment-26 Hi Aaron Putting something together about integration with Transfer is a great idea. I will put up some thoughts about it shortly. Thanks for the suggestion. Hi Aaron

Putting something together about integration with Transfer is a great idea. I will put up some thoughts about it shortly. Thanks for the suggestion.

]]> By: Aaron Lee http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/comment-page-1/#comment-25 Aaron Lee Thu, 05 Jun 2008 20:25:17 +0000 #comment-25 Very useful library. Thanks for sharing Kevan! Have you tried integrating this with Transfer ORM? I'd love to hear your thoughts on this. Aaron Very useful library. Thanks for sharing Kevan!

Have you tried integrating this with Transfer ORM? I’d love to hear your thoughts on this.

Aaron

]]> By: Kevan Stannard http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/comment-page-1/#comment-24 Kevan Stannard Sun, 01 Jun 2008 13:18:05 +0000 #comment-24 Adam, thanks for raising this. I will look into adding locking. For the transaction handling I am considering leaving that for the calling code for now. Adam, thanks for raising this. I will look into adding locking. For the transaction handling I am considering leaving that for the calling code for now.

]]> By: Adam Cameron http://blog.stannard.net.au/2008/05/30/nested-set-trees-in-coldfusion/comment-page-1/#comment-23 Adam Cameron Sat, 31 May 2008 09:32:59 +0000 #comment-23 What is your position on handling "race conditions" which could crop up by a subsequent call to - for example - moveToNextSibling() whilst a previous call to it is still running, so that the queries end up running like this: Request 1: updateLeft Request 2: updateLeft Request 1: updateRight Request 2: updateRight Rather then the required: Request 1: updateLeft Request 1: updateRight Request 2: updateLeft Request 2: updateRight Your tree data will become corrupted. I was caught out by this with my initial implementation of this sort of thing, in high-traffic situations. You might want to put some locking or transactionality around your queries. -- Adam What is your position on handling "race conditions" which could crop up by a subsequent call to – for example – moveToNextSibling() whilst a previous call to it is still running, so that the queries end up running like this:

Request 1: updateLeft
Request 2: updateLeft
Request 1: updateRight
Request 2: updateRight

Rather then the required:

Request 1: updateLeft
Request 1: updateRight
Request 2: updateLeft
Request 2: updateRight

Your tree data will become corrupted. I was caught out by this with my initial implementation of this sort of thing, in high-traffic situations.

You might want to put some locking or transactionality around your queries.

–
Adam

]]>