We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 4385
    • 372 Posts
    I have a simple table. A points table. I would like to leverage modx authentication. Can I have 200,000 users? They would login to check their points. The user manager would be a bit unwieldy, but I would probably create a snippet to handle updates.

    This question has been answered by sottwell. See the first response.

      DropboxUploader -- Upload files to a Dropbox account.
      DIG -- Dynamic Image Generator
      gus -- Google URL Shortener
      makeQR -- Uses google chart api to make QR codes.
      MODxTweeter -- Update your twitter status on publish.
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      Don't see why not. The user list is paged, so it won't bother the Manager any.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        I would use ClassExtender to extend the user class to hold the points, though, unless you want to use one of the existing fields. You definitely don't want to use the extended fields.

        If you use one of the existing fields, you can change its label in the lexicon so nobody will forget what it's supposed to be.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 4385
          • 372 Posts
          An existing field would be faster. So 200,000 wouldn't be problem? I doubt their would be very many concurrent users.
            DropboxUploader -- Upload files to a Dropbox account.
            DIG -- Dynamic Image Generator
            gus -- Google URL Shortener
            makeQR -- Uses google chart api to make QR codes.
            MODxTweeter -- Update your twitter status on publish.
          • discuss.answer
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            Yes, you could use the "fax" field perhaps. Hardly anybody has a fax number any more. And it would take a lot more the 200,000 records in a database table to cause a problem. Here's a discussion a few years ago, and things have only improved since then. http://stackoverflow.com/questions/2716232/maximum-number-of-records-in-a-mysql-database-table
              Studying MODX in the desert - http://sottwell.com
              Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
              Join the Slack Community - http://modx.org
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              Concurrent users would have nothing to do with how many users there are in the database, that would be related to how many concurrent requests can your database server handle. And that is totally up to the server configuration. Cheap shared hosting frequently causes database access failures, but that has nothing to do with the size of the database, only with how many hits can the server handle. Moving to a better shared hosting company (such as SkyToaster) invariably solves these problems.
                Studying MODX in the desert - http://sottwell.com
                Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                Join the Slack Community - http://modx.org