Hi John, John McNally wrote:
>The types available are mostly a subset of java.sql.Types. The only >exceptions are BOOLEANINT and BOOLEANCHAR which exist to allow a common >practice of defining an INT (0,1)or CHAR (Y,N) column to hold boolean >values. Maybe I should not have even added these extra types. I don't >see much reason to add a special DATETIME torque type. It seems what >you might want to do, if you need the DATE jdbc type to map to mysql's >DATE is to define > >TIMESTAMP=DATETIME >DATE=DATE > >in db.props > Thanks for giving the information that these things are defined in db.props - that's really helpful. This adjustment would make PostGre and MySQL interpretation of my schema more consistent. However, this doesn't cover the situation where I might want to have both DATETIME and TIMESTAMP columns in a single MySQL table. The point is that DATETIME and TIMESTAMP give different functionality in MySQL. I think James is probably right that we would prefer so be taking control of date updating (rather than letting the database do it automatically), so not supporting the MySQL TIMESTAMP column type seems the way to go. Although I don't know if other databases make a distinction between TIMESTAMP and DATETIME. CHEERS> SAM -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
