Hi Denis,
I'm not sure exactly what you mean by "turning off dynamic sql". There are several attributes on the <table> element that will turn off certain statements (enableSelectByExample="false", enableDeleteByExample="false", etc.) Does that meet your need? (If the "*byExample" statements are disabled, there won't be any dynamic SQL in the map)
I think the superclass is an interesting idea. It would be the superclass of the primary key if the table had a primary key, or the superclass of the "record" class otherwise. Is that what you're thinking?
Jeff Butler
On 12/11/05, Denis Vladimirov <[EMAIL PROTECTED]> wrote:
Hi Jeff,
I found the problem. That table was a synonim, so I have just changed schema name to the schema name that owns that table and it works.
Would be nice to have an option where you specify a super class for the Model you are going to generate like this :
<javaModelGenerator targetPackage="test.model" targetProject="vlad">
<property name="enableSubPackages" value="true" />
<property name="trimStrings" value="true" />
<property name="superClass" value="AbstractModel" />
</javaModelGenerator>
also would be nice to have an option of turning On and Off dyanmicSQL for some tables, like this:
<table schema="COMMON" tableName="PARAMETERS" domainObjectName="Parameter" >
<property name="useActualColumnNames" value="true"/>
<property name="createDynamicSQL" value="true"/> <!-- default is false -->
</table>
Otherwise its exellent tool
Regards,
Denis
