Golden Deer Pub Community Forums

Barring any further setbacks, my own stupidity included, I should be able to be done with this tonight!

@_@ holy shit, I wasted a fucking hour on my own damn stupidity.

I needed a primary key. At first I thought it a good idea to make the names of an entry a primary key. So I whipped it up and then had to make codes to handle duplicate entries since they crashed the program.

Then I realized... shit... <_< a person of a different ID wouldn't be able to have the same name in the address book either! How to create an ID of some sort that is automatically generated but will not cause this issue....

So I made a field that will not show up named "PK" (Primary Key AND Player Killer - I LOVE IT!! *cough*) that is generated by the user's ID+Name fields.

EXCEPT IT WAS STILL REGISTERING AS DUPLICATE ENTRIES!! I spent an hour trying to come up with every godforsaken PK I could think up. Finally I then ripped out my error handling codes as a last ditch attempt of desperation - maybe I hadn't done it right. That's when I realized... oh my codes are perfect... I just didn't update them. I still had the program looking at the Name field for duplicates. x_x Replaced it with the PK variable and it works like a charm now. I can't believe I did that. How I overlooked it. I made the PK variable and updated the SQL commands, but I forgot that one small step. *sigh*



T-T baka ja nai.... baka ja nai!!

?? Then what do you use to make your primary key?

As for finding and deleting the right record, that'll be easy, just let SQL do the work for you.

Kimiko - I think you are misunderstanding this program.

I set the table up on the SQL side and then the rest is run through Java.

I don't think I understand. Are you saying that you're doing more than the UI in Java? Why try to duplicate SQL's excellent database handling?

So, school.

It's where you learn.

[spoiler]To be a man![/spoiler]