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