Martin Poeschl <[EMAIL PROTECTED]> writes:
>Jon Scott Stevens wrote:
>>I always see us make commits for fixing reserved words in databases.
>>
>>Why not come up with a .properties file of reserved words for each database
>>and then as part of the initial load of the .xml file, simply query that
>>file and see if one of the column/table names conflicts with the database of
>>reserved words...we can have a property which turns this feature on or off
>>(for example, some people might not that db2 conflicts with oracle or
>>something like that...)
>>
>>-jon
>>
>how will this work if i want to make sure my app runs with different
>databases?? (e.g. jetspeed)
As I understood jon, this list would be as database specific as e.g. the
SQL dialect understood be the engine. So the wordlist would be tied to
the adapter for the database.
I'm definitely +1 on this. We might even have some sort of closure (set of
all words forbidden in all databases, which will help your problem).
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
