Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

Issue Confirmations

  • Yes (0)No (0)
Photo

`char`.`name` -> UNIQUE

Posted by Hercules Bot on 20 April 2012 - 06:33 AM

Originally posted by Kenpachi
`name` column in `char` table should be unique because 3rd party tools like control panels could produce errors.

Originally posted by Kenpachi
Fixed in [rev=16490].

Originally posted by Lemongrass
I thought *Athena isn't going to apply according to 3rd party tools rather they have to apply to *Athena.
Anyways if you're already at fixing the data structures in SQL would you mind adding foreign keys to the tables?

Originally posted by Kenpachi
Well, since someone told me that a nooby 3rd party tool doesn't check for duplicate names and creates them I was forced to add this to the DB layout. ^_^

We do have many foreign keys already. For example:
- `char`.`account_id`
- `char`.`party_id`
- `char`.`guild_id`
- many more

Just because they aren't connected hard in the DB layout it doesn't mean they are no foreign keys... but I'll discuss this with the other developers (again ^^).

Originally posted by Lemongrass
I know that those are foreign keys. But in truth or as they are they are no real foreign keys, which means there is no consistency check.

Additionally some usage of the "ON DELETE CASCADE" feature would be very nice. It would give administrators a huge benefit during the cleaning of their database(s).