<span class="gmail_quote"></span>I've used 'text' for content, as I think it will contain text only data<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
(serialized php variables). If you need binary data, then use bytea, but<br>you'll have to use db_{encode,decode}_blob() functions.</blockquote><div><br>If 'text' works for serialized objects, then that's probably what I need. Maybe in mySQL, too. I was just concerned that a text field would top out at 255 characters, and I wasn't sure how many I'd end up with.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I've also added default values because iirc mysql will insert '' if<br>there is no default and no value is provided.
</blockquote><div><br>Good point. Shouldn't be an instance where there *isn't* a value, but it's a good habit.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would suggest changing 'uid' name to something else, as it's reserved<br>name.</blockquote><div><br>Good point. Is 'type" ok? I've seen it elsewhere (e.g. Nodes) but I wasn't sure...<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> COMMENT ON COLUMN subscriptions_holding.rid IS 'Unique row ID';<br>...<br>> COMMENT ON COLUMN subscriptions_holding.uid IS 'The person performing the operation';<br><br>Those are also good, if you really want comments.
</blockquote><div><br>Why wouldn't you? Is there a cost? Otherwise, anything that explains what's going on can only help in later troubleshooting, no?<br></div><br></div>-- <br>Dan Ziemecki<br>Philosopher. Curmudgeon. Nerd.