summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--feature/composite/interface-type2
-rw-r--r--feature/composite/list2
-rw-r--r--feature/list6
-rw-r--r--feature/query/container2
-rw-r--r--feature/query/list2
-rw-r--r--feature/view/list2
-rw-r--r--feature/view/object-loading2
7 files changed, 6 insertions, 12 deletions
diff --git a/feature/composite/interface-type b/feature/composite/interface-type
index a5f61ab..a3f346b 100644
--- a/feature/composite/interface-type
+++ b/feature/composite/interface-type
@@ -1,3 +1,5 @@
+Interface type for existing composite value types
+
Some existing value types (e.g., time_period in Boost.DateTime) do not
provide modifiers and the only way to initialize such types is by passing
everything at once in a constructor. For such types it would be nice to
diff --git a/feature/composite/list b/feature/composite/list
index 8a9c257..fcd824d 100644
--- a/feature/composite/list
+++ b/feature/composite/list
@@ -1,5 +1,3 @@
-- Interface type for existing composite value types: interface-type
-
- Make column prefix for locally-defined composite value types empty
If a composite value type is defined in a class, then we could make
diff --git a/feature/list b/feature/list
index c47f926..446f03e 100644
--- a/feature/list
+++ b/feature/list
@@ -1,9 +1,3 @@
-* Documentation: doc/
-* Composite value: composite/
-* Container: container/
-* Query: query/
-* View: view/
-
- load_value() that returns object by value, similar to query_value()
That would be both the database class function as well as the query
diff --git a/feature/query/container b/feature/query/container
index 76c005e..262f2b3 100644
--- a/feature/query/container
+++ b/feature/query/container
@@ -1,3 +1,5 @@
+! Support containers in queries
+
- Parts of a container query:
* selector -- selects which elements are examined
diff --git a/feature/query/list b/feature/query/list
index 8cd922d..39c85ca 100644
--- a/feature/query/list
+++ b/feature/query/list
@@ -1,5 +1,3 @@
-- Support containers in queries: container
-
- Implement and document how to call stored procedures in each DB
Also some DBs distinguish between procedures and functions. Need
diff --git a/feature/view/list b/feature/view/list
index 61b108e..33024ac 100644
--- a/feature/view/list
+++ b/feature/view/list
@@ -1,5 +1,3 @@
-! Object loading views [2.4.0]: object-loading
-
- Member names for table views
Currently we have to specify column names as strings in table views queries.
diff --git a/feature/view/object-loading b/feature/view/object-loading
index 478d098..8ecabb2 100644
--- a/feature/view/object-loading
+++ b/feature/view/object-loading
@@ -1,3 +1,5 @@
+! Object loading views [2.4.0]
+
- The joined object can be joined just to be used in the query condition or
to load the data. How to distinguish the two cases and what should be the
default?