update TODO
[dbsrgits/DBIx-Class-Schema-Loader.git] / TODO
CommitLineData
0f1f51e0 1- General
2 - High Priority
3 - clean out RT queue
4 - introspect views and make proper ResultSource::View classes with defining SQL
5 - encode loader options in Schema.pm
6 - introspect on_update/on_delete/is_deferrable
7 - preserve_case mode for remaining backends
8 - Low Priority
9 - support multiple/all schemas, instead of just one
10 - support pk/uk/fk info on views, possibly (materialized views?)
11 - remove deprecated ResultSetManager stuff, rewrite using current features
12 - 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.
13 - support for user-defined-types as Schema deploy hooks
14 - normalize float/real/double data types in a most cross-deployment friendly fashion, using float(25) as the double boundary where possible
15 - finish data_type tests for all DBs (DB2 and Oracle left)
16 - support for Informix
17 - generate a schema accessor which stores which SQLT type it was loaded from
18 - add a settable 'on-behalf-of' version tag (for catalyst model)
19 - inject a table2moniker function into the schema
20 - support coderef for relationship_attrs
21 - common tests for table/column comments
22 - optimize queries
23 - remove extra select for _filter_tables
bc5afe55 24 - option to promote non-nullable unique constraints to PK (prefer int
25 columns when more than one) (RT#51696)
d3677651 26 - normalize accessors for mixed case columns in v7 mode (FooBar -> foo_bar)
16f6b6ac 27
0f1f51e0 28- Relationships
29 - Re-scan relations/tables after initial relation setup to find ->many_to_many() relations to be set up
30 - 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?)
a13b2803 31
0f1f51e0 32- Backends
33 - SQLite
34 - table/column comments
35 - introspect on_update/on_delete/is_deferrable
36 - introspect view SQL
37 - MySQL
38 - table/column comments
39 - introspect on_update/on_delete/is_deferrable
40 - introspect view SQL
41 - Pg
42 - introspect on_update/on_delete/is_deferrable
43 - introspect view SQL
44 - preserve_case mode
45 - DB2
46 - data_type tests
47 - table/column comments
48 - introspect on_update/on_delete/is_deferrable
49 - introspect view SQL
50 - preserve_case mode
51 - Oracle
52 - data_type tests
53 - table/column comments
54 - introspect on_update/on_delete/is_deferrable
55 - introspect view SQL
56 - preserve_case mode
57 - Sybase ASE
58 - table/column comments
59 - introspect on_update/on_delete/is_deferrable
60 - introspect view SQL
61 - MSSQL
62 - table/column comments
63 - introspect on_update/on_delete/is_deferrable
64 - introspect view SQL
65 - computed column support
66 - Optimization
67 - use one query for whole table instead of query-per-column in _columns_info_for
68 - use placeholders when available
69 - SQLAnywhere
70 - table/column comments
71 - introspect on_update/on_delete/is_deferrable
72 - introspect view SQL
73 - preserve_case mode
74 - Firebird
75 - table/column comments
76 - introspect on_update/on_delete/is_deferrable
77 - introspect view SQL
1b291d2c 78 - Informix
79 - data_type tests
80 - preserve_case mode
81 - table/column comments
82 - introspect on_update/on_delete/is_deferrable
83 - introspect view SQL