2 support multiple/all schemas, instead of just one
4 support pk/uk/fk info on views, possibly. May or may not be a sane thing to try to do.
6 Fix up ResultSet Manager / Methods / etc stuff. May require some work in the
7 main DBIx::Class first.
9 SQLite needs some heavy refactoring, the subroutines are becoming too complex to understand easily.
11 Refactor RelBuilder so that it doesn't require a live mostly-built
12 DBIx::Class::Schema, so that other modules (SQLT) can use it easier. And then
13 when/if we get there, break it out as a seperate distribution with a new name.
16 If local column is UNIQUE or PK, use has_one() for relation?
17 Re-scan relations/tables after initial relation setup to find ->many_to_many() relations to be set up?
18 Check NULLability of columns involved in the relationship, which might suggest a more optimal non-default -join-type?
19 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?)