On Fri, 9 Feb 2001, Dirk Zimmermann wrote:
> 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.
You know better than we do what the keywords are for your DB
product. It is not the place of our persistence manager to keep extensive
lists of all keywords for all versions of all DB products so they get
escaped properly if you try to use them as a table or column name. This
is not a flaw of JBoss; if you set up JBoss to use MSSQL then you won't
have a problem with Interbase keywords. Also, the workaround doesn't
interfere with your EJB logic - it's a setting in your deployment
descriptor.
Aaron
