Update of /home/cvsd/slony1/slony1-engine
In directory main.slony.info:/tmp/cvs-serv26552

Modified Files:
	TODO 
Log Message:
Remove TODO items now in Bugzilla items 11, 12, 13

Index: TODO
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/TODO,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** TODO	22 Nov 2007 22:58:42 -0000	1.14
--- TODO	22 Nov 2007 23:02:06 -0000	1.15
***************
*** 24,40 ****
    NODE and UPDATE FUNCTIONS.
  
- - Script to "duplicate node"; create a new node that looks just like
-   an existing node, that is, with the same replication sets.
- 
-   Overview:
-    - Run slony1_extract_schema.sh against the origin node for the sets
-      subscribed to; this gives an SQL script.
- 
-    - Generate slonik script to do:
-      * STORE NODE for new node
-      * STORE PATH to get the new node to communicate with the node it's
-        duplicating
-      * SUBSCRIBE SET for all the relevant sets
- 
  - Need to draw some "ducttape" tests into NG tests
  
--- 24,27 ----
***************
*** 54,78 ****
  ---------------------------
  
- - Add more tests (what???) to test_slony_state script(s).
- 
-   e.g. - add a warning if there exist tables with generated PK.
- 
-   Arguably, that isn't really a good thing to do; if there is a table
-   with column generated via TABLE ADD KEY, then we have the
-   undesirable result that there will be an error/warning reported
-   every time test_slony_state is run.
- 
-   Perhaps there should be a second script that looks for "static"
-   problems, so we can leave test_slony_state to look for "dynamic"
-   problems.
- 
- - Partitioning Support
- 
-   Add stored procedures to support adding in subscriptions to empty
-   tables; verify emptiness on origin, TRUNCATE on subscribers.  The
-   stored proc(s) would be run as part of EXECUTE SCRIPT...
- 
- - Use PGXS
- 
  - Windows-compatible version of tools/slony1_dump.sh
  
--- 41,44 ----