Aaron Mulder writes:
> In your jaws.xml file, you can specify alternate column names for
> each CMP field, so you could call the column "ejb_password" or whatever.
>
> Aaron
>
Yes, that's perfectly alright, but IMHO it comes close to changing the
fields of my entity only because I use SQL. I don't want to track
problems with SQL when I deal with my ejb logic. It should be easy to
'escape' such magic strings in the PersistanceManager when constructing
SQL. The example was from a working app in an Inprise AppServer with
MSSQL, and there were never problems.
I could hack something in, but I would prefer to discuss a solution
with a DB-Mapping, so you can configure JAWS in a clean way to escape
certain magic strings, dependent on the DB it uses.
--
/// Dirk.
