summaryrefslogtreecommitdiff
path: root/feature
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2015-02-07 15:45:19 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2015-02-07 15:45:19 +0200
commitd0f8d15c414ba48bb1015c01db8f37a32fa1acbd (patch)
tree6798fb37c717a852baf17da558c07615287f012a /feature
parent32406157c439f3750770157eb947ee2d63d7e020 (diff)
Add feature: Schema to C++ classes
Diffstat (limited to 'feature')
-rw-r--r--feature/list12
1 files changed, 12 insertions, 0 deletions
diff --git a/feature/list b/feature/list
index 18ae045..33226a4 100644
--- a/feature/list
+++ b/feature/list
@@ -1,3 +1,15 @@
+- Schema to C++ classes
+
+ http://codesynthesis.com/pipermail/odb-users/2014-January/001769.html
+
+ What if instead of all these mappings, customizations, etc., we
+ just provide a template (or a plugin) and let the user write/customize
+ some C++ code to produce a mapping that they want?
+
+ Another idea: define database schema tables as persistent classes?
+ What if the generator is basically an ODB-based application that
+ the user is expected to customize?
+
- ON UPDATE clause in generated schema
Would be nice to be able to specify this similar to on_delete.