X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=a2ba73f1d5eb805c263d7d6b72e4490ac9ac5132;hb=b08ea624f7e059f3236724a50ed648ed204170d5;hp=8db718c2155bfc4b5583d503eef00aa06dcfe1e4;hpb=c2849787d7804fcbe541c8063e240ceff0e5ff10;p=dbsrgits%2FDBIx-Class-Schema-Loader.git

diff --git a/TODO b/TODO
index 8db718c..a2ba73f 100644
--- a/TODO
+++ b/TODO
@@ -1,14 +1,22 @@
+OTHER STUFF
+===========
 
-Reminders to myself or whoever else ever looks in here...
+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.
 
 SQLite needs some heavy refactoring, the subroutines are becoming too complex to understand easily.
 
-Relationship-building needs to be refactored into a seperate module to share with SQLT.
+Refactor RelBuilder so that it doesn't require a live mostly-built
+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:
-   Fix multiple rels between same pair of tables
-   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?)
-...
+   ...
+
+unregister sources for dropped tables on rescan