Adam,<div><br></div><div>ModComments is a mine of data, your are right direction we are interested in the your prototype.</div><div><br></div><div>I take the blame of introducing the varchar field on parent_comments - it should be integer, will add it to my list. I was planning for a simple tool that can aid developers to detect such inconsistency let me know if you had one.</div>
<div><br></div><div>Regards,</div><div>Prasad</div><div><br><div class="gmail_quote">On Thu, Feb 7, 2013 at 11:07 PM, Adam Heinz <span dir="ltr"><<a href="mailto:amh@metricwise.net" target="_blank">amh@metricwise.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I'm prototyping a feature where comments are aggregated. For example, if I'm viewing comments on an Account, I might want to see all comments for the Contacts associated with the Account. The reverse could also be true; maybe I want to see the Account comments if I'm looking at a Contact.</div>
<div><br></div>I notice there is already a vtiger_modcomments.parent_comments column in the database, but it appears to be unused in 5.4.0. What is the intended purpose of this field?<br><div><br></div><div>On a somewhat related note, why are the related_to and parent_comments fields VARCHAR? Shouldn't they either be INTEGER or broken out into a join table? I am really not a fan of putting a bunch of database ids into a field separated by semicolons; SQL really doesn't handle that sort of shenanigans very well.</div>
<div><br></div></div>
<br>_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br></blockquote></div><br></div>