What is the MySQL extension for?

Discussion in 'Rust Discussion' started by Austinv900, Mar 9, 2016.

  1. Austinv900

    Austinv900

    What does the MySQL plugin actually do?

    Is it possible to make Oxide Group permissions have the ability to be managed by SQL?
    ex. change group permission on sql database. Group updated on server.
     
    Austinv900, Mar 9, 2016
    #1
  2. Wulf

    Wulf Community Admin

    The MySQL extension provided by Oxide allows plugins to add MySQL support. Permissions with Oxide are managed via the .data files only, but a plugin could be made to sync them with a database.
     
    Wulf, Mar 9, 2016
    #2
  3. Austinv900

    Austinv900

    That would be so awesome if that plugin was made.
     
    Austinv900, Mar 9, 2016
    #3
  4. sqroot

    sqroot

    What use would that have?
     
    sqroot, Mar 9, 2016
    #4
  5. Mr. Skritz

    Mr. Skritz

    If people were to purchase some kind of VIP feature or access to some kind of command, they wouldn't have to wait for an admin to get on to apply it, it would be applied straight away. Therefor decreasing the amount of people who would get angry and charge back. I know there would be a LOT of people who would want to see this plugin be made
     
    Mr. Skritz, Mar 9, 2016
    #5
  6. Wulf

    Wulf Community Admin

    You could handle that without storing data in MySQL, just webrequests and using your payment system's API, and some simple commands to grant the permissions automatically once a payment is detected. There are plugins that already handle this too, mostly paid though.
     
    Wulf, Mar 9, 2016
    #6
  7. Austinv900

    Austinv900

    Picture having separate tables labeled for your groups Admin, Mod, Player. Doesn't need to have a fancy setup. Just one column under each group. Permission per row. Permissions would be easily edited, added, or removed with phpmyadmin or some other SQL editor. Won't have to worry about people messing up setting permission because of everything being in a table format
     
    Austinv900, Mar 9, 2016
    #7
  8. sqroot

    sqroot

    Why would it be any different from just editing the protobuf data file directly?
    In fact, the server could even call the respective commands to manage permissions and such directly (if you have to change it from outside via a simple RCON script), there'd be no need to access the data file (or an sql frontend for that matter) directly.
    [DOUBLEPOST=1457558421][/DOUBLEPOST]
    I honestly don't really see how this fixes the issue that people might be able to mess with things.
    If people are able to mess things up using the commands, then why would a table change anything about that?
    Also, keep in mind that permissions offer a bit more than what you suggested, such as inheritance.
     
    sqroot, Mar 9, 2016
    #8