Anybody know a good workaround for errors in om code generation due to
a column of type TIMESTAMP being used as a primary key ? Not that
anyone should use a timestamp as a primary key :) but just supposing
they were ... the following code gets generated in the base Object
class:
public void setPrimaryKey(ObjectKey key) throws TorqueException
{
SimpleKey[] keys = (SimpleKey[]) key.getValue();
SimpleKey tmpKey = null;
setStupidId(keys[0].toString());
setCreationDate(((DateKey)keys[1]).getDate());
)
setStupidNo(((NumberKey)keys[2]).byteValue());
}
Notice the bonus close paren.
-Dave
|