Why does Torque (on some databases) use a VARCHAR when a CHAR is
requested by the schema column definition?

According to the db.props file it does this for the following
databases:  db2400 db2 hypersonic interbase mssql postgresql sapdb

Databases that Torque uses CHAR for CHAR are: cloudscape oracle sybase

I am not familiar with all the databases Torque works with, but I do
know that CHAR works fine with JDBC on PostgreSQL.

-james

-- 
[]  James A. Hillyerd <[EMAIL PROTECTED]> - Java Software Engineer
[]  PGP 1024D/D31BC40D F87B 7906 C0DA 32E8 B8F6 DE23 FBF6 4712 D31B C40D


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to