Jason van Zyl <[EMAIL PROTECTED]> writes:
> On 6/13/01 4:56 AM, "Unico Hommes" <[EMAIL PROTECTED]> wrote:
>
> > In database.dtd for torque it specifies that I can use the value BINARY for
> > the type attribute of the column element. However when I try to use it the
> > generated peer sources cannot be compiled. Is this a known issue? The same
> > thing happens for BOOLEANCHAR. I am using BOOLEANINT instead now but it
> > seems a waste as it translates to INT(11) in Mysql.
>
> There is a db.props file for each database type in torque. In the
> turbine CVS tree it's location in
> conf/torque/templates/sql/base/<db>/db.props. It very well may be
> that the mapping of types is not complete. I will take a look ...
> Upon looking at the db.props for MySQL it appears that the JDBC
> BINARY type has no mapping, we should fix that :-) Right now VARBINARY
> maps to a MEDIUMBLOB for MySQL.
Coincidently, I added the mapping for the JDBC BINARY type for MySQL
yesterday in CVS HEAD (to BLOB--JDBC BLOB is also now mapped to MySQL
LONGBLOB).
> Is BOOLEANCHAR a JDBC type. The type used for a column in a Torque
> schema are strictly the JDBC types _not_ native db types.
That is a good question. There are some data types available from the
Torque DTD that have no mapping in any of the Torque db-specific
properties files (i.e. BOOLEANCHAR). Who can answer this question and
provide a supporting URL for documentation?
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
