X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=ee048c45579c975f1e6872b1cd1d4b454ee3fe92;hb=254ba31ccf3d09c814e8267019b00775878347e5;hp=ab176b0cd106bcacc156a5a20e5374a66af400b7;hpb=b97c2c1e790cc4c18370238fd98eddac4e7de2d8;p=dbsrgits%2FDBIx-Class-Schema-Loader.git

diff --git a/TODO b/TODO
index ab176b0..ee048c4 100644
--- a/TODO
+++ b/TODO
@@ -1,3 +1,10 @@
+0.05 BLOCKERS
+=============
+
+Add backwards-compatibility mode when regenerating a 0.04-generated schema
+
+OTHER STUFF
+===========
 
 support multiple/all schemas, instead of just one
 
@@ -13,8 +20,6 @@ DBIx::Class::Schema, so that other modules (SQLT) can use it easier.  And then
 when/if we get there, break it out as a seperate distribution with a new name.
 
 Relationship stuff:
-   If local column is UNIQUE or PK, use has_one() for relation?
    Re-scan relations/tables after initial relation setup to find ->many_to_many() relations to be set up?
-   Check NULLability of columns involved in the relationship, which might suggest a more optimal non-default -join-type?
    While scanning for many-to-many, scan for implied rels as well? (if foo->belongs_to('bar') and baz->belongs_to('bar'), does that impliy foo->might_have('baz') and the reverse?)
    ...