Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Message-Id: <5.1.0.14.2.20030801130024.02e1dca0@mail.snowball.com>
Date: Fri, 01 Aug 2003 13:03:52 -0700
To: "Apache Torque Users List" <torque-user@db.apache.org>
From: Geoff Fortytwo <g42@ign.com>
Subject: different internal variable names
In-Reply-To: <20030801170202.GA4576@fs1.t-sys.hu>
References: <Law11-OE43VbvWRkRau0000e3b3@hotmail.com>
 <E140F7BF5ED11A47AEE830C6FF0FA4C04E6195@opc-sec-ex1.sec.gov>
 <Law11-OE38ssssGKeD50000e130@hotmail.com>
 <oprs8daiz3ht3xnm@mail.t-sys.hu>
 <Law11-OE43VbvWRkRau0000e3b3@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

This topic was talked about on this list recently, but no one seemed to 
suggest a solution.

If I have a table column named "short" then that'll screw things up because 
that's a reserved java keyword, so a variable can't have that name. 
Assuming that the column name can't be changed (due to lots of other apps 
already using the table) then is the only solution to modify the velocity 
code so that, for instance, all internal variables have an underscore 
appended to them? That solves the problem for all possible java reserved 
name conflicts.

But is there a way to fix this without modifying velocity? The javaName 
column only fixes the names of the functions, it doesn't alter the internal 
variable names.


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org