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


immediate stuff for 0.04:
--------------------------

avinash240 wants a rescan method to pick up new tables at runtime

-------

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.

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