Adam,<div><br></div><div>We plan to take up data-type consistency while we pickup schema architecture improvement.</div><div>As this inconsistency has crept in while the product was too early... fixing them would take sometime.</div>
<div><br></div><div>Please update (<a href="http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/7429" target="_blank">http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/7429</a>) when you come across others.</div><div><br></div><div>
Thanks for your efforts!!</div><div><br></div><div>Regards,</div>
<div>Prasad</div><div>
<br><br><div class="gmail_quote">On Thu, May 31, 2012 at 10: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">
Whoops. I just wasted a few minutes because I forgot that for<br>
vtiger_products.discontinued, 0 means true and 1 means false, but for<br>
vtiger_crmentity.deleted, 1 means true and 0 means false. Has any<br>
thought been given to consistently representing booleans in the<br>
database? Per mysql documentation<br>
<br>
<a href="http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html" target="_blank">http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html</a><br>
BOOL, BOOLEAN<br>
These types are synonyms for TINYINT(1). A value of zero is<br>
considered false. Nonzero values are considered true:<br>
_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>
</blockquote></div><br></div>