A mac question regarding the installation of the JLex scanner

Question

Hi
I'm trying to run JLex on my Mac running Tiger and Java 5. I am trying to run JLex but when I try and run the program I keep getting exceptions.
I think the problem here is with the classpath. I've been looking around online and can't seem to find directions for altering the classpath on a mac.
The instructions for installing and running JLex aren't proving enough for me to get it to work. These instructions are:
Written by Elliot Berk  [edited by A. Appel] [revised by C. Scott Ananian].
Contact [email protected] with any problems relating to JLex.
The following steps describe the compilation and usage
of JLex.
(1) Choose some directory that is on your CLASSPATH, where
    you install Java utilities such as JLex.  I will refer
    to this directory as "J", for example.
(2) Make a directory "J/JLex" and put the sourcefile Main.java
    in J/JLex.
(3) Compile Main.java as you would any Java source file:
javac Main.java
This should produce a number of Java class files, including Main.class,
in the "J/JLex" directory, where "J" is in your CLASSPATH.
(4) To run JLex with a JLex specification file,
the usage is:
java JLex.Main <filename>
where <filename> is the name of the JLex
specification file.  If java complains that
it can't find JLex.Main, then the directory
"J" (which contains the subdirectory "JLex"
which contains the class files) isn't in your
CLASSPATH; go back and read steps 1-3 more
carefully, please.I am guessing the problem I am having here is with setting the class path on a mac. If anyone can give me some help with this I would be really grateful.

Answer 1

Creating this sort of trigger, though
- would require that the user create triggers for every table they create
- wouldn't prevent the user from deleting or disabling the trigger, deleting rows, and then re-enabling the trigger
If I own a table, I will always be able to delete, insert, and update rows in that table. That's one of the privileges of ownership.
I suppose that you could grant a user CREATE ANY TABLE privileges, let them create tables in another schema, and then have DDL triggers that only grant them appropriate privileges on those new objects. The CREATE ANY TABLE privilege, though, would be a huge security hole...
Justin