NickName (dadada@rock.com) writes:
> The next day, the colleague told me our boss has another solution, that
> is, he joins this same table twice to geneate a fourth column of
> another pkID, and it works perfect and it's very elegant compared to my
> approach.
>
> Question here is, would you know/use his approach without learning this
> techque? Second question is, would there be any downside on using
> this alternative approach of creating a parent to child relationship
> for the same table not using PK column?

So what did his solution look like?

I don't see the point of not using pkID/parentID, but then again, I
don't know the actual business problem.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx