I am just about to complete grading 52 student projects. The projects are email 
clients. Every submission has SQL scripts that I must run before I can run the 
student code. Randomly, without a pattern I can detect, the SQL scripts run 
with errors claiming a table is missing. When this happens I just run the 
script that creates the database and the second script that creates the tables 
and inserts test data. The problem escalates when suddenly these scripts won't 
run without errors claiming that the database does not exist as well as more 
missing tables. I go to the Services tab, open the root connection to the MySQL 
DB and I see the db and tables. If I run a script with just "drop database 
xxxx;" it tells me the script ran fine but when I look it is still there. At 
one point I resorted to running the scripts in MySQL Admin and they worked 
fine. The student code using JDBC runs without any of these problems especially 
as part of the unit tests they have a routine that runs the create tables 
script.

Coming from an era when the first trouble shooting task was to reboot, I closed 
NB 12.0 and then restarted it. Suddenly the scripts that failed work for a few 
student submissions and then it happens again. I do not know how to write this 
up for jira. I don't thing saying "Sometimes it doesn't work" is a solvable 
problem. Does anyone else run SQL scripts in NetBeans multiple times in a 3 to 
4 hour period?

Suggestions?

[cid:[email protected]]
Ken Fogel
Faculty
email: [email protected]<mailto:[email protected]>
phone: (514) 931-8731 local 4799
Dawson College, 3040 Sherbrooke St. W Westmount, Quebec, H3Z 1A4, Canada
[facebook icon]<https://www.facebook.com/ken.fogel> [twitter icon] 
<https://twitter.com/omniprof>  [youtube icon] 
<https://www.youtube.com/kenfogel>  [linkedin icon] 
<https://www.linkedin.com/in/kenfogel/>  [instagram icon] 
<https://www.instagram.com/omniprof/>
[cid:[email protected]]<https://www.dawsoncollege.qc.ca/>          
 [cid:[email protected]]             
[cid:[email protected]]


Reply via email to