![]() If that key needs to be unique throughout the lifetime of the product, then it shouldn't be user-chosen. On a software development level, the principle problem is choice of unique key. The problem was that the key in this case was a commonly-used value that would make it hard to avoid. Their suggestion was to access the underlying database and delete the unique key. Since the software maintains a unique key throughout its lifetime, that key should not be destroyed. However, the developers response was that it was not a bug. The error on creation was " Another account is already using this unique key." but the user interface shows no such key in use anywhere. ![]() The steps shown demonstrated that "deleting" something didn't allow it to be recreated afterwards. I recently submit a bug report about a user interface.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |