Fix =head level for some constructor options.

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

diff --git a/TODO b/TODO
index 00ac47d..6b90994 100644 (file)
--- a/TODO
+++ b/TODO
@@ -4,16 +4,15 @@
     - introspect views and make proper ResultSource::View classes with defining SQL
     - encode loader options in Schema.pm
     - introspect on_update/on_delete/is_deferrable
-    - preserve_case mode for remaining backends
   - Low Priority
     - support multiple/all schemas, instead of just one
     - support pk/uk/fk info on views, possibly (materialized views?)
     - remove deprecated ResultSetManager stuff, rewrite using current features
-    - 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.
+    - 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.
     - support for user-defined-types as Schema deploy hooks
-    - normalize float/real/double data types in a most cross-deployment friendly fashion, using float(25) as the double boundary where possible
-    - finish data_type tests for all DBs (DB2 and Oracle left)
-    - support for Informix
     - generate a schema accessor which stores which SQLT type it was loaded from
     - add a settable 'on-behalf-of' version tag (for catalyst model)
     - inject a table2moniker function into the schema
@@ -29,10 +28,18 @@
     - add hashref form of generate_pod to control which POD is generated
     - add hashref form of components to control which components are added to
       which classes
+    - check rel accessors for method conflicts
+    - add an option to add extra code to Result classes (maybe...)
+    - redo in-memory schema as an @INC coderef rather than temp files
+    - add option to filter out views
+    - support columns with names like "ro'd p/n" in MSSQL
 
 - Relationships
-   - Re-scan relations/tables after initial relation setup to find ->many_to_many() relations to be set up
-   - 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?)
+   - Re-scan relations/tables after initial relation setup to find
+     ->many_to_many() relations to be set up
+   - 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?)
 
 - Backends
   - SQLite
@@ -47,21 +54,16 @@
   - Pg
     - introspect on_update/on_delete/is_deferrable
     - introspect view SQL
-    - preserve_case mode
     - domains
   - DB2
-    - data_type tests
     - table/column comments
     - introspect on_update/on_delete/is_deferrable
     - introspect view SQL
-    - preserve_case mode
     - domains
   - Oracle
-    - data_type tests
     - table/column comments
     - introspect on_update/on_delete/is_deferrable
     - introspect view SQL
-    - preserve_case mode
     - domains
   - Sybase ASE
     - table/column comments
@@ -81,7 +83,6 @@
     - table/column comments
     - introspect on_update/on_delete/is_deferrable
     - introspect view SQL
-    - preserve_case mode
     - domains
   - Firebird
     - table/column comments
@@ -90,7 +91,6 @@
     - domains
   - Informix
     - data_type tests
-    - preserve_case mode
     - table/column comments
     - introspect on_update/on_delete/is_deferrable
     - introspect view SQL