Hi > -----Original Message----- > From: Daniel Rall [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, June 20, 2001 2:54 PM > To: [EMAIL PROTECTED] > Subject: Re: oracle db.props (was: torque and oracle number data > type) > > "Chris Campbell" <[EMAIL PROTECTED]> writes: > > > > The RAW type requires a size in oracle. So, when I try to create > > > application, there is a problem with Turbine's tables using VARBINARY > > > types without size. Either the problem is in the db.props and the > > > assignment should be something like: > > > VARBINARY = LONG RAW > > > or the problem is in turbine-schema.xml and it has to include the size > > > for the columns with VARBINARY type. > > > > > > > Problem with LONG RAW is there can only be one per table in Oracle. I > would > > suggest changing the turbine-schema so you don't limit your own tables > to > > one varbinary > > Indeed, Chris orates the truth. When I found this out about Oracle, I > changed the JDBC/Torque VARBINARY type to map to a Oracle RAW, and set > the mapping for LONGVARBINARY to Oracle LONG RAW. Gabriel, you are > correct that a SIZE parameter will have to be specified now when one > uses VARBINARY for a schema used with Oracle. I realize that this is > not symmetrical with the mappings for MySQL, but thought that it would > be more flexible. If you like, you could do what I did for some of > the other Oracle mappings and provide a SIZE which would be the > equivalent of a MySQL MEDIUMBLOB. Thoughts on this? > > Daniel Rall > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
