I think it happens because (at least) torque creates static constants in
peers with field names. # is definitely not a valid identifier char in java.
So the answer is that currently you can only use columns which names are
valid java identifier names. I do not think this is a big problem. Of course
torque can be hacked to strip away any illigal chars. Still column names
starting with numbers or containing spaces may be a problem...
fedor
> -----Original Message-----
> From: Daniel Rall [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 08, 2001 2:26 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Torque can't deal with special chars.
>
>
> Jason Kary <[EMAIL PROTECTED]> writes:
>
> > I'm not sure if this is the right list, but I thought I
> would let you
> > know that Torque (in TDK 3.1a5) can't deal with the
> character '#' when
> > creating an object model. Apparently oracle accepts '#' as
> part of a
> > column name.
>
> Do you get an XML parsing error, or is the error from Torque itself?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
