[Bps-public-commit] r11576 - in SVN-PropDB: . doc

[jesse at bestpractical.com]

Author: jesse
Date: Sun Apr  6 00:21:57 2008
New Revision: 11576

Modified:
   SVN-PropDB/   (props changed)
   SVN-PropDB/doc/todo
   SVN-PropDB/t/simple-push.t

Log:
 r29357 at 31b:  jesse | 2008-04-05 18:16:18 -1000
 * t/simple-push.t now contains a failing test. alice and bob should have the same replica uuid if they're going to sync


Modified: SVN-PropDB/doc/todo
==============================================================================
--- SVN-PropDB/doc/todo	(original)
+++ SVN-PropDB/doc/todo	Sun Apr  6 00:21:57 2008
@@ -2,29 +2,12 @@
         
     - write tests for RT-prophet-prophet-hiveminder sync
     
-    - implement uuids for prophet databases
-    
-        - On initialization of an empty prophet replica 
-            - get a uuid
-            - set replica's 'db_root' to _prophet-UUID
-        
-        
-            - how do we tell prophet what db uuid it wants to use if there are two of them? or do we expect one replica to only ever have one database?
             
-            - how to mark two uuid as joined? 
-                - merging between two replicas with different uuids is basically saying "I want to merge these two different databases"
-                - it should be possible to _change_ a replica's uuid. but maybe not for 0.1
-                - merging between replicas that were seperately initialized is to be treated as hm. "ow"
-                - sane?
                 
-            
-            - and does it mean if the db is initialized with a pull, it uses the same UUID
+      - make merge aware of database uuids
+                - and does it mean if the db is initialized with a pull, it uses the same UUID
                 - yes. in general, dbs should be initialized with pull or be new projects
-                   
-            
-           - (use the uuid as a prefix for the db root?)  
-        - each replica should know the uuid of the database it is a replica of
-        - merging between replicas with different uuids should require a 'force' argument of some kind.
+                - merging between replicas with different uuids should require a 'force' argument of some kind.
 
     - light dinner
 
@@ -52,6 +35,10 @@
     - extract the reusable bits of Prophet::Replica::RT to
             Prophet::ForeignReplica
 
+    - implement uuids for prophet databases DONE
+    
+
+
 
 
 Todo after saturday:

Modified: SVN-PropDB/t/simple-push.t
==============================================================================
--- SVN-PropDB/t/simple-push.t	(original)
+++ SVN-PropDB/t/simple-push.t	Sun Apr  6 00:21:57 2008
@@ -3,7 +3,7 @@
 use warnings;
 use strict;
 
-use Prophet::Test tests => 9;
+use Prophet::Test tests => 10;
 
 as_alice {
     run_ok( 'prophet-node-create', [qw(--type Bug --status new --from alice )], "Created a record as alice" );
@@ -29,6 +29,9 @@
 my $alice = Prophet::Replica->new( { url => repo_uri_for('alice') } );
 my $bob   = Prophet::Replica->new( { url => repo_uri_for('bob') } );
 
+
+is ($bob->prophet_handle->db_uuid, $alice->prophet_handle->db_uuid, "bob and alice's replicas need to have the same uuid for them to be able to sync without issues");
+
 my $changesets = $bob->new_changesets_for($alice);
 
 my $openbug = '';