Author: wyoung
Date: Tue Mar 3 18:21:47 2009
New Revision: 2475
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2475&view=rev
Log:
Pushed several v3.1 section items off to 3.2.
Modified:
trunk/Wishlist
Modified: trunk/Wishlist
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/Wishlist?rev=2475&r1=2474&r2=2475&view=diff
==============================================================================
--- trunk/Wishlist (original)
+++ trunk/Wishlist Tue Mar 3 18:21:47 2009
@@ -186,6 +186,43 @@
- Replace CREATE TABLE SQL in resetdb with create_table() calls.
+ o Try to add Query::storein(container, ssqls), which generates
+ SELECT * from {ssqls.table()} and stores the result. May not be
+ possible due to existing overloads, but try. If it works, use
+ this form in the userman Overview section, saving one LOC.
+
+ o Add Query::storein<Container, T>(container), getting table
+ name from container::value_type.table() instead.
+
+ o Define operator<< for Fields, Row, StoreQueryResult, etc., giving
+ CSV format.
+
+ o Define operator<< for sequence_container<SsqlsBase> and similar
+ for associative containers. Give mysql(1)-like ASCII grid or
+ some other table format.
+
+ o Remove libexcommon. Between above and SSQLSv2, we should have
+ everything we need to get equivalent output without special
+ purpose code. There should be no ad hoc data dumping code in
+ the examples.
+
+ o Bring back mandatory quoting for manipulators? If someone says
+ os << mysqlpp::escape << foo; do they not really really mean
+ escape foo? Automatic quoting and escaping is different. See
+
+ http://lists.mysql.com/plusplus/7999
+
+ o Configure script should try to get MySQL C API directories
+ from mysql_config.
+
+ o If pkg-config is available, register ourselves with it using
+ information discovered by configure. Also, write out a
+ mysql++-config script, which either wraps pkg-config or
+ reinvents it, poorly, for systems that don't have it.
+
+
+v3.2 Tentative Plan
+-------------------
o Chris Frey's packarray class
o Create adaptors for std::bitset, for storing binary data in a
@@ -203,14 +240,6 @@
o Add a general-purpose backtick manipulator as well.
- o Define operator<< for Fields, Row, StoreQueryResult, etc. In other
- words, there should be a way to get a user-readable version of
- received data without a lot of code. CSV format by default, and
- mysql(1)-like ASCII grid optionally, perhaps with a manipulator?
- There is grid code in examples/multiquery.cpp which we can use
- and then make multiquery.cpp a demonstration platform for it.
- Maybe dbinfo and fieldinf, too?
-
o Has experience with new thread awareness changed our mind on
atomic inc/dec of reference counts in RefCounted*?
@@ -220,11 +249,6 @@
o Optional checked conversions in String for numerics: throw
BadConversion on range overflow?
-
- o Try to add Query::storein(container, ssqls), which generates
- SELECT * from {ssqls.table()} and stores the result. May not be
- possible due to existing overloads, but try. If it works, use
- this form in the userman Overview section, saving one LOC.
o Add Query::storein_if(), mirroring store_if()
@@ -233,31 +257,8 @@
wstring, C++/CLI native strings, etc. Then convert examples that
do this conversion to use this new mechanism.
- o Bring back mandatory quoting for manipulators? If someone says
- os << mysqlpp::escape << foo; do they not really really mean
- escape foo? Automatic quoting and escaping is different. See
-
- http://lists.mysql.com/plusplus/7999
-
- o Configure script should try to get MySQL C API directories
- from mysql_config.
-
- o If pkg-config is available, register ourselves with it using
- information discovered by configure. Also, write out a
- mysql++-config script, which either wraps pkg-config or
- reinvents it, poorly, for systems that don't have it.
-
o Try to add operator std::string to String. If it doesn't work,
explain why not in the userman, and in Row::operator[] refman.
-
- o Try to get away from libexcommon? Maybe move everything into
- mysqlpp::examples namespace and build it as part of MySQL++-
- the-library, so people trying to fork an example to create
- something new don't have to worry about these routines.
- Keep the sources in examples/ so Doxygen doesn't complain
- about the routines being undocumented. Some routines can
- eventually be replaced by already-proposed future features,
- like the ability to do pretty dumps of SSQLSes.
v4.0 or Later
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
