Commit | Line | Data |
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) |
16f6b6ac |
26 | |
0f1f51e0 |
27 | - Relationships |
28 | - Re-scan relations/tables after initial relation setup to find ->many_to_many() relations to be set up |
29 | - 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 |
30 | |
0f1f51e0 |
31 | - Backends |
32 | - SQLite |
33 | - table/column comments |
34 | - introspect on_update/on_delete/is_deferrable |
35 | - introspect view SQL |
36 | - MySQL |
37 | - table/column comments |
38 | - introspect on_update/on_delete/is_deferrable |
39 | - introspect view SQL |
40 | - Pg |
41 | - introspect on_update/on_delete/is_deferrable |
42 | - introspect view SQL |
43 | - preserve_case mode |
44 | - DB2 |
45 | - data_type tests |
46 | - table/column comments |
47 | - introspect on_update/on_delete/is_deferrable |
48 | - introspect view SQL |
49 | - preserve_case mode |
50 | - Oracle |
51 | - data_type tests |
52 | - table/column comments |
53 | - introspect on_update/on_delete/is_deferrable |
54 | - introspect view SQL |
55 | - preserve_case mode |
56 | - Sybase ASE |
57 | - table/column comments |
58 | - introspect on_update/on_delete/is_deferrable |
59 | - introspect view SQL |
60 | - MSSQL |
61 | - table/column comments |
62 | - introspect on_update/on_delete/is_deferrable |
63 | - introspect view SQL |
64 | - computed column support |
65 | - Optimization |
66 | - use one query for whole table instead of query-per-column in _columns_info_for |
67 | - use placeholders when available |
68 | - SQLAnywhere |
69 | - table/column comments |
70 | - introspect on_update/on_delete/is_deferrable |
71 | - introspect view SQL |
72 | - preserve_case mode |
73 | - Firebird |
74 | - table/column comments |
75 | - introspect on_update/on_delete/is_deferrable |
76 | - introspect view SQL |
1b291d2c |
77 | - Informix |
78 | - data_type tests |
79 | - preserve_case mode |
80 | - table/column comments |
81 | - introspect on_update/on_delete/is_deferrable |
82 | - introspect view SQL |