Wes Hardaker wrote:
>
> I'd suggest concentrating on
> enable as many features as possible, but allow them to be disabled
> from the module implementation when not possible. Meaning, the module
> writer should be able to dictate whether tables can be left open or
> should be reopened.
I will definitely be making all of the things I have discussed (and
other changes from the current SQL::Statement) *options* which can be
turned on or off by the subclass writer. The subclass writer then also
can either enforce one mode for most options, or pass them on as choices
to the user, i.e. make a given option settable via flags in the connect
statement or elsewhere at the discretion of the subclass writer.
--
Jeff
