Jump to content
  • Table permissions changed in an update!


    Xenithar
    • Status: Completed
      Main Category: Database
      Sub-Category: sqlupdate
      Version: 2.0.11 Milestone: 20 Priority: High
      Implemented Version: 0.20

    Access is suddenly denied!

    I dropped my world DB tonight while working on another problem. I recreated it and used the "FullDB" directory to fill it. Then I went about applying updates. 20003_05 and 20003_06 worked like a charm. I stopped at 20003_07 because suddenly I am denied access to "creature_movement". This may be related to the message I posted in the developer forum about mobs flying despite having mmaps. I can correct this, but something happened somewhere which changed my permissions during one of the updates or the install.

    Oh, and I have done this twice now. Each time I use my root user to grant access to the world DB.
    [code]
    GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, LOCK TABLES ON `zp_world`.* TO ''@'localhost';
    [/code]
    When that 07 update hits, it denies access every time.


    User Feedback

    Recommended Comments

    Xenithar

    Posted

    I figured it out. Patch 07 is VERY flawed. Broken, to be exact. Well, the first working line of code, anyway. Let me past the working lines of code here.
    [code]
    UPDATE mangos.creature_movement SET model1 = 308 WHERE id = 80119;
    UPDATE creature SET position_x = -8840.38, position_y = -271.402, position_z = 80.9516, orientation = 1.12229, modelid = 308 WHERE guid = 80119;
    UPDATE creature SET orientation = 4.936845 WHERE guid = 19379;
    UPDATE creature SET position_x = -2376.782227, position_y = -1962.498413, position_z = 96.087646, orientation = 0.773024 WHERE guid = 19382;
    [/code]
    Note line #1. It specifies the DB name as "mangos.*". I do not use that. My DB is so old it still has the "zp" prefix (Zero Project for those who do not know). The line needs to be changed to remove "mangos." and it will work. Changing status of this ticket.

    Chucksta

    Posted

    This has already been fixed, PR'd and merged with the core DB.

    [B][SIZE=3][COLOR="#800080"]This issue can be considered resolved[/COLOR][/SIZE][/B]



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use