The first one that I thought was pretty cool was something that took a memory model (in tabular format) and generated the necessary CREATE TABLE commands to build the table, complete with primary key and foreign key constraints. Then it took that output (in the Unix pipe-lining philosophy) and checked that each of the tables primary key types matched the foreign key types when they appeared in other tables; another script ordered the commands, so that the independent tables appeared first, followed by the dependent tables.
It impressed the hell out of the senior consultant on the contract, which didn't hurt. It definitely sold me on the value of Perl as an Open Source tool. I sure wish I'd made copies of those scripts. That was in about '98, and (I think) Perl 5 had just come out. Good times.
PS Oh yeah, all built without actual access to an SQL database .. I just looked up the appropriate syntax on-line. Such a geek.
Alex / talexb / Toronto
Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.
-
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.
|
