Re: [SQLObject] Re: datetime column conversions

[Barry W. <ba...@py...>]

On Wed, 2005-01-05 at 20:12, Jorge Luiz Godoy Filho wrote:

> One thing that I was thinking about was making it optional.  Something li=
ke
> adding a parameter "auto_cast=3DFalse" (default) or "auto_cast=3DTrue" wh=
en
> instantiating the class.  If it is true, then what is read from the
> database is passed through a conversion to the type it was supposed to be=
.
>=20
> Another option was to add a "cast_method=3DMethod" where the default is
> "None".  If it is a method then everything read from the database is pass=
ed
> to it (where one can make the cast to the desired type with some
> 'isinstance' checks of the object).  It might be used for other things --
> filters come to my mind -- too.=20

I think I would like to see a standard protocol or interface defined for
these things.  Then I could pass an instance of an object in that
conformed to the protocol to do the type conversion in either or both
directions (it shouldn't be required to include them both).  If you
decide to split validation and conversion, then those protocols would be
defined too.  I think it's fine to define the base column types as
converting to and from the standard Python types.

-Barry