Jason van Zyl <[EMAIL PROTECTED]> writes:
> On 8/21/01 4:13 PM, "Daniel Rall" <[EMAIL PROTECTED]> wrote:
>
> > Jason van Zyl <[EMAIL PROTECTED]> writes:
> >
> >> On 8/21/01 2:35 PM, "Daniel Rall" <[EMAIL PROTECTED]> wrote:
> >>
> >>> I am working on correcting this. The issue is that the TorqueSQLTask
> >>> now needs access to the database adapters.
> >>
> >> Why? I don't think that's very good. I would eventually like to use the SQL
> >> generation stand-alone and this addition will make that very hard. Isn't
> >> there any other way?
> >
> > For solid SQL generation, I need to the RDBMS-specific maximum column
> > length. The natural place for this is the DB adapters (since they
> > hold database-specific idiosyncrasies). I am open to other
> > suggestions.
>
> How about in the db.props file?
I'll give it a try. We may actually be able to push more db-specific
meta information in that direction.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
