Glitch with Adoptables hard-deletion
|
04-24-2012 10:38 AM
|
|
Administrator, Lead Coder
|
|
Glitch with Adoptables hard-deletion
The glitch exists if you are trying to hard-delete a species that has already been adopted/pounded
Well tbh I havent looked into how the hard-deletion works for an adoptables species, but apparently its causing some troubles already. When a pet is hard-deleted from ACP, the script attempts to delete all records associated with it. But apparently, it is not doing as good a job as expected.
The rows in table prefix.adoptables and prefix.owned_adoptables are deleted, but not with the rows in table prefix.pounds. For this reason the Pound center is malfunctioning if an admin ever tries to delete an active pet(a pet that has been adopted and pounded) from ACP. This glitch is not affecting the most of you 'cause its occurrence requires the following double-coincidence:
1. The adoptables have been hard-deleted from the system through ACP.
2. Prior to its deletion from system, the adoptables have been adopted and pounded.
Fixing this problem should be easy, will post a solution soon.
|
|
Issue Details
|
Category Unknown
Status Fixed
Priority 6
Affected Version Mys v1.3.1
Fixed Version Mys v1.3.2
Users able to reproduce bug
1
Users unable to reproduce bug
0
Assigned Users
(none)
Tags
(none)
|
|
06-03-2012 09:14 PM
|
|
I haven't looked at any of the tables, but are you using INNOdb? If yes, why aren't you using foreign keys in order to enforce referential integrity. That way you can even set it up so that the delete cascades.
~judda
|
All times are GMT -5. The time now is 10:54 AM.
Currently Active Users: 862 (0 members and 862 guests)
Threads: 4,080, Posts: 32,024, Members: 2,016
Welcome to our newest members,
jolob.