![]() Phil's sync will cause a violation of the unique constraint.Ĭurrently, Zumero does not have any mechanism to allow for alternative handling of regular UNIQUE constraint or UNIQUE index violations. The server's database goes to version 2, with his row inserted into the ![]() Lew does: INSERT INTO foo (a,b) VALUES ('rose', 16) Phil does: INSERT INTO foo (a,b) VALUES ('rose', 16) We start the example with Phil, Lew and the server all at version 1 of the The database contains one synchronized table, defined as: TABLE foo: (įoo_id uniqueidentifier PRIMARY KEY DEFAULT NEWID(), You can manage passwords outside Zumero, as you did before. This will allow ZSS Manager to change user names and manage permissions,īut any password changes are silently ignored. ers view with id, name and pass columns, but write the insert/update triggers such that only If you have existing users and passwords in your database but passwords are neither plain text norīcrypt hashes, you can still use ZSS Manager to set permissions, which is recommended. Non-unique users will lead to unpredictable results, or to failed sync. It is strongly recommended that the and columns be unique. ![]() This table is used to determine group membership. If you wish to use existing groups, you must create a view, oups, with columns ThisĬould cause problems for other applications if they're not expecting passwords in this format. If you change a user's password with ZSS Manager, it will be encrypted with bcrypt. Insert and update triggers that handle the name and pass columns. If you want to use ZSS Manager to alter users and passwords, the view you create must have You must create a view, ers, with columns, , and. (A mix of both in the same table will work.) Passwords must be either plain text or bcrypt hashes. Migrating ZSS Configuration between Servers 7.3. Constraint Violations and Conflict Resolution 6.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |