As much as I prefer to avoid serialized data when possible, there are cases where it makes sense. What is the general purpose of this move? What are the repercussions for modules which use this column in D6? Does core use this column?
<br><br>..chrisxj<br><br><div><span class="gmail_quote">On 11/22/06, <b class="gmail_sendername">Karoly Negyesi</b> <<a href="mailto:karoly@negyesi.net">karoly@negyesi.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>Two steps<br><br>a) We remove $user->data handling code from D6 core. No save, no load. New<br>installs won't have this column.<br>b) D7 will drop the $user->data if it exists. (SELECT * FROM user,<br>$account = db_fetch_array, if(isset($account['data'])) -- no need for DDL
<br>to check for a column).<br><br>This way D6 contribs can clean up $user->data and migrate to their own<br>tables.<br><br>Regards<br><br>NK<br></blockquote></div><br>