I don't think there is a problem with it at all. I've done it before. That's what its there for.<br><br>To build on Brian's comments though you should use it in conjunction with hook_install/uninstall using db_add/drop_field in those functions and letting the schema API know about it in hook_schema_alter<br clear="all">
-----<br>Adam A. Gregory<br>Drupal Developer & Consultant<br>Web: AdamAGregory.com<br>Twitter: <a href="http://twitter.com/adamgregory">twitter.com/adamgregory</a><br>Phone: 910.808.1717<br>Cell: 919.306.6138<br>
<br><br><div class="gmail_quote">On Mon, Jul 12, 2010 at 12:30 PM, Brian Vuyk <span dir="ltr"><<a href="mailto:brian@brianvuyk.com">brian@brianvuyk.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">
I don't see any problem with it, although I would add / remove the
columns with hook_install() / hook_uninstall() rather than
hook_schema_alter().<br><font color="#888888">
<br>
Brian</font><div><div></div><div class="h5"><br>
<br>
On 10-07-12 12:19 PM, nan wich wrote:
<blockquote type="cite">
<div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: rgb(127, 0, 63);">
<div>Is there an official stance on using hook_schema_alter to
add columns to core tables? For example, we collect additional data on
anonymous comments and want to actually save that data. Rather than
creating another table (and subsequent JOINs), I'd just as soon stuff
that data into the comments table, where it belongs. Should we ever
disable comments (unlikely), we probably wouldn't mind losing that data
too.<br>
</div>
<p><font size="4" color="#ff007f" face="bookman old style, new york, times, serif"><i><b>Nancy E. Wichmann, PMP</b></i></font></p>
<p><font face="arial, helvetica, sans-serif">Injustice anywhere is a
threat to justice everywhere. -- Dr. Martin L. King, Jr.</font></p>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br>