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
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
13 DBIx::Class::Schema, so that other modules (SQLT) can use it easier. And
14 then when/if we get there, break it out as a seperate distribution with a
16 - support for user-defined-types as Schema deploy hooks
17 - finish data_type tests for all DBs (DB2 and Informix left)
18 - generate a schema accessor which stores which SQLT type it was loaded from
19 - add a settable 'on-behalf-of' version tag (for catalyst model)
20 - inject a table2moniker function into the schema
21 - support coderef for relationship_attrs
22 - common tests for table/column comments
24 - remove extra select for _filter_tables
25 - option to promote non-nullable unique constraints to PK (prefer int
26 columns when more than one) (RT#51696)
27 - figure out how to represent Informix 'DATETIME YEAR TO FRACTION(5)' in a
28 way that SQLT will like
29 - support domains (aka custom data types) as a Schema deploy hook
30 - add hashref form of generate_pod to control which POD is generated
31 - add hashref form of components to control which components are added to
33 - add original => {} to all type info rewrites
34 - add common tests for preserve_case option
35 - correct handling of CamelCase names with numbers (eg. foo2Bar -> Foo2Bar,
37 - check rel accessors for method conflicts
38 - add an option to add extra code to Result classes
41 - Re-scan relations/tables after initial relation setup to find
42 ->many_to_many() relations to be set up
43 - While scanning for many-to-many, scan for implied rels as well (if
44 foo->belongs_to('bar') and baz->belongs_to('bar'), does that impliy
45 foo->might_have('baz') and the reverse?)
49 - table/column comments
50 - introspect on_update/on_delete/is_deferrable
53 - table/column comments
54 - introspect on_update/on_delete/is_deferrable
58 - introspect on_update/on_delete/is_deferrable
64 - table/column comments
65 - introspect on_update/on_delete/is_deferrable
70 - table/column comments
71 - introspect on_update/on_delete/is_deferrable
76 - table/column comments
77 - introspect on_update/on_delete/is_deferrable
81 - table/column comments
82 - introspect on_update/on_delete/is_deferrable
84 - computed column support
87 - use one query for whole table instead of query-per-column in _columns_info_for
88 - use placeholders when available
90 - table/column comments
91 - introspect on_update/on_delete/is_deferrable
95 - table/column comments
96 - introspect on_update/on_delete/is_deferrable
102 - table/column comments
103 - introspect on_update/on_delete/is_deferrable
104 - introspect view SQL