It has clearly come to my attention that for this class I need to be VERY VERY explicit about the database lab.

I know that you have things going on at your places of employment and might want to test Java on them. I am happy about that...but it is just fine with me if you just think of this particular lab as testing of Java and Databases rather than try to fit it in too closely with your job.

So, you should get an account on our Oracle (or currently MySQL) database, and make your system work on it. If your firewalls prevent you to do it from your machines, then get an account on our machines and do it remotely. If this prevents you from having beautiful GUI's... you can still test what you want it to do (regarding DB access) without a GUI

get an account on our database
use Update your existing account
follow the directions at
http://www.ecst.csuchico.edu/~amk/foo/advjava/notes/database/lab0.html
Other than adding the driver to your CLASSPATH, editing the URL and driver specification in your own code to match the example, and making sure you import the right things you should not have to change much else
OK, given the above here is the grading template for the database lab:
11 points for the lab:
```
-2 if didn't use the database here via the URL
   +1 back if you can show me errors of you *trying*  to
      use it, but got significant errors (i.e., not errors 
      like not being able to find the driver, etc)

+3 for complexity Specifically
   +0 trivial -it connected and could access the database
   +1 average -no big deal but you did more than copy the examples
   +2 good
   +3 great (did not just use lesson examples with a different application)


+5 if it runs

+2 documentation (ADTs, OMs, explanation, what it does, etc)

+1 readme
```
Notice, this means if you run the database *here*, you can get 9 (A-) points for having an average (no big deal) lab
Also, points taken off of the 5 for "it runs" as follows:
If you are using oracle use

That's it...I hope!
Thanks
Anne
A reply from a student who has been working in this:
There is a positive way to look at all these "problems" we are having getting this database stuff to work - we are learning, firsthand, what some of the most very important problems are. If we work through them, the experience will be invaluable. For example, I *never* knew that SQL was different from vendor to vendor. When I first got my program working with Access, I felt a little guilty, because it had been so easy! I've easily spent 10 times the hours trying to "port" my app to a different database vendor. Also, busting through the firewall and having the database so slow has caused me to have to go back in and change my UI so the user can tell it didn't die or something. All good stuff....