fix POD coverage and t/backcompat/0.04006/23dumpmore.t

[dbsrgits/DBIx-Class-Schema-Loader.git] / TODO

diff --git a/TODO b/TODO
index 7a7439f..ee048c4 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,7 +1,14 @@
+0.05 BLOCKERS
+=============
 
-dump_to_dir needs an overwrite flag, and needs to not overwrite by default
+Add backwards-compatibility mode when regenerating a 0.04-generated schema
 
-dumping needs to pick up columns_info_for data
+OTHER STUFF
+===========
+
+support multiple/all schemas, instead of just one
+
+support pk/uk/fk info on views, possibly.  May or may not be a sane thing to try to do.
 
 Fix up ResultSet Manager / Methods / etc stuff.  May require some work in the
 main DBIx::Class first.
@@ -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?)
    ...