Regarding dynamic SQL - I think the capability you need is already in Abator. The XML configuration for the table element allows you to "turn off" the generation of any (or all) statements for a table. A configuration like this should do what you want:
<table schema="foo" tableName="bar" enableSelectByExample="false"
enableDeleteByExample="false" />
(Sorry this isn't better documented. It's all in the DTD, but that can be kind of hard to read)
Jeff Butler
On 12/11/05, Denis Vladimirov <[EMAIL PROTECTED]> wrote:
Hi Jeff,
That would be a superclass of the "record" class. All our model classes extend the same AbstractModelClass which has some common functionality for the all Models
I'm not sure exactly what you mean by "turning off dynamic sql".
I meant turning off the generation of the dynamic sql methods/mappings in the DAOs and in the SQL map for some tables.
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?
Regards,
Denis
