There is a similar, more broad mantra which I have come to employ in some recent database work - Think about how you're actually going to use the data. Spending some time to address this question early in the database design process has allowed for some very significant improvements in some code which I am working on currently. In a similar fashion to demerphq, time stamp entries across a series of database tables in some code that I am working with is now stored in an unsigned integer as seconds since epoch - Furthermore, aided by the MySQL internal commands for address conversion, some network mapping database entries are now stored in long integer format and as such, some large portions of network address calculations in userspace have been able to be removed and replaced by internal MySQL address conversion functions. eg.
perl -le "print unpack'N', pack'B32', '00000000000000000000001000000000'"
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
