> > Currently, it is not possible in Torque 4 to use a sql type which is
not
> > mapped by a Torque type. E.G the torque type TIMESTAMP is mapped to
the
> > SQL type DATETIME in mysql, and it is not possible to create a column
with
> > SQL type TIMESTAMP out of the box.
> > Therefore I propose to add an attribute "sqlType" to the column Element
in
> > whihc the default sql type can be overridden.
> >
> > Any objections ?
>
> In Liquibase which tries to make database maintenance DBMS-independent,
> they decided to support the Java SQL types (java.sql.Types.*) as an
> alternative. I'd propose to do the same here. See the explanation at
> http://www.liquibase.org/manual/column This would work without extra
> attributes.
The liqibase manual says:
"Also, specifying a java.sql.Types.* type will be converted to the correct
type as well "
This is exactly what we do, the Schema types Torque uses are 1:1 those of
java.sql.Types
The question is what to do if our correct mapping is not the mapping the
user wants....
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
