path: root/feature/list
diff options
authorBoris Kolpackov <>2015-03-13 17:02:29 +0200
committerBoris Kolpackov <>2015-03-13 17:02:29 +0200
commitbba5278e13d00781989e448c1ac2d8e5d339502d (patch)
treed82796b21a76e6d549ac8f47e80f37a98b42d4f4 /feature/list
parent9365373c0c476576b9d346413a0dcad2a111e6dc (diff)
Add feaure: Ability not to generate schema for certain objects/containers
Diffstat (limited to 'feature/list')
1 files changed, 23 insertions, 0 deletions
diff --git a/feature/list b/feature/list
index 9544186..5206ca3 100644
--- a/feature/list
+++ b/feature/list
@@ -1,3 +1,26 @@
+! Ability not to generate schema for certain objects/containers
+ Sometimes it can be useful to overlay an object onto existing
+ (or another object/container) table. This is possible now for
+ object if one is careful with order but not for containers.
+ Perhaps an explicit no_schema pragma?
+ Once this is fixed, diagnose using of abstract classes in views.
+ See email from <>/13-Mar-2015.
+! Primary key in to-many container table
+ Can we add 'unique' (similar to 'unordered') to container of object
+ pointers data member that says no duplicate pointers. We can then
+ generate a primary key based on the two ids. In fact, should we not
+ do this by default?
+ The other way to achieve the same end result would be via the support
+ for container indexes (i.e., add unique index based on the two).
+ See email from <>/13-Feb-2015.
! Virtual data member only handle simple type specification
Right now there is no way to say virtual(void*) or virtual(nullable<int>).