Too bad you aren't checking whether your actions succeed,
and neither are you using transactions when you are modifying
your database. Now your examples are equivalent of Perl code
that isn't strict, doesn't have warnings turned on, and isn't
checking the return values of system calls.
There's no execuse to not wrap your database modifying
statements inside a transaction, and to not rollback on
As for checking for the existance of a table, that's
rather easy in Sybase and MSSQL:
WHERE name = "whatever" -- Name of the table
AND type = "U" -- User defined table.
-- Use "S" for a system table.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.