|
One of my users has raised an issue:
Due to safety filters at work, OpenID is not an option for this user. Is this a limitation at the database end? My site is running SVN-980, and using SQL Lite. |
|
The max length of the username is 30 characters and the max length of the user email is 75 characters. This limits are exposed by the Django django.contrib.auth application which is used by OSQA, so we cannot extend that limitation. Consider updating to the latest trunk version of OSQA. A bunch of improvements were made and we also warn users with longer usernames and emails when they external OpenID providers. Also IMO it's dubious to use SQLite as database backend, especially for production. Im in the process of upgrading, just struggling with what to do. Do u have any links on reasoning behind not using SQLLite? I heard it was ok unless your site gains high traffic?
(29 Aug '11, 08:25)
Simon
The upgrade should be as simple as "svn update". IMO SQLite is fine for testing and development databases. It's not perfect for big databases. I suppose you want your community to grow without pains. :)
(29 Aug '11, 09:04)
Jordan ♦♦
Will look into migrating to MySQL. Will also need to do some research around SVN as a lot of people keep recommending it. Just not too clued up with SSH.
(29 Aug '11, 09:24)
Simon
|
@Simon, all meta.osqa.net postings are required to have a clear, specific question in their title field. Please correct the title of this posting right away. Thanks.