Torque 3.0-b4 bug in OM generation for Oracle

[Joe McGlynn]

I am seeing two bugs in Torque 3.0 B4, I've only been using Torque for a few
hours, but I don't think this is my error.  If someone could give a quick
synopsis of how to troubleshoot and fix these sort of issues I'd be happy to
submit fixes next time.

I have a table definition as follows:

    <table name="Workflow"
           description="Contains all XML-based workflows for the system">
        <column name="ID" primaryKey="true" required="true"  type="BIGINT"/>
        <column name="Name" required="true" size="64" type="VARCHAR"/>
        <column name="WorkflowType_ID" required="true"  type="BIGINT"/>
        <column name="AssistTLevel_ID" required="true"  type="BIGINT"/>
        <column name="CONTENT" default="EMPTY_CLOB()" required="true"
type="BLOB"/>
        <column name="DeleteFlag" default="'0'" required="true"
                size="1" type="CHAR"/>
        <column name="ReservedFlag" default="'0'" required="true"
                size="1" type="CHAR"/>
        <column name="LastUpdate" default="SYSDATE" required="true"
type="TIMESTAMP"/>
    </table>

When I run the om ant target it generates a BaseWorkflow.java as follows:

        private byte[] content = new byte[](EMPTY_CLOB() );
                    (note the parends instead of curly braces)

If I change the type attribute on "CONTENT" to "CLOB" (which is what I want
it to be) then I get:

        private String content = "EMPTY_CLOB()";

Also, the generated code for "LastUpdate" ends up like this:

        private Date lastupdate = new Date(SYSDATE);