After all there is a way how to handle user insertion cross-db

sbsdev · Nov 26, 2009 · 9126296 · 9126296
1 parent 16839bd
commit 9126296
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 5 deletions.
diff --git a/documents/sql/state.sql b/documents/sql/state.sql
@@ -32,7 +32,9 @@ INSERT INTO auth_group (id, name) VALUES (3, 'Proof_Readers');
 INSERT INTO auth_group (id, name) VALUES (4, 'Approvers');
 
 -- add a demo user
--- is unfortunately backend specific and therefore handled in state.*.sql
+INSERT INTO auth_user (id, username, first_name, last_name, email, password,
+       is_staff, is_active, is_superuser, last_login, date_joined) 
+VALUES (2, 'demo', 'Demo', 'User', 'demo.user@example.com', 'sha1$7f00f$139ae061147ffafd825cfec2951d86e787959aef', '0', '1', '0', '2009-11-26 16:23:51.949691','2009-11-26 16:23:37.074040');
 
 -- add groups to demo user
 INSERT INTO auth_user_groups (id, user_id, group_id) VALUES (1, 2, 1);

diff --git a/documents/sql/state.sqlite3.sql b/documents/sql/state.sqlite3.sql