Author: wyoung
Date: Fri Mar 10 22:50:51 2006
New Revision: 1244
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=1244&view=rev
Log:
Merged v2.0 Wishlist changes into the v2.1 branch copy
Modified:
branches/v2.1-bakefile/Wishlist
Modified: branches/v2.1-bakefile/Wishlist
URL:
http://svn.gna.org/viewcvs/mysqlpp/branches/v2.1-bakefile/Wishlist?rev=1244&r1=1243&r2=1244&view=diff
==============================================================================
--- branches/v2.1-bakefile/Wishlist (original)
+++ branches/v2.1-bakefile/Wishlist Fri Mar 10 22:50:51 2006
@@ -28,6 +28,30 @@
possible to subclass yourself from the "MySQL++'s developers"
base class.
+
+ o Someone reported needing more than 12 parameters in a templatized
+ query. We can just add some more overloads, but we should take
+ the opportunity to see if there's a cleaner way to handle this.
+
+ o The manual recommends using "0, 0" as the second and third
+ parameters for creating SSQLSes, but this doesn't actually
+ compile. Try to enumerate all the possible function overloading
+ problems in the manual, and come up with a solid recommendation
+ that will always work. "1, 0" seems to work on a lot of code, but
+ we should know _why_ it works.
+
+ o Viktor Stark reports that a BLOB of binary data containing 0's
+ appears to be truncated when stored in an SSQLS with a std::string
+ for the BLOB field. Investigate, and fix if confirmed.
+
+ o Document restrictions on order of destruction. See this thread:
+ http://lists.mysql.com/plusplus/5084
+
+ o Storing a subset row in an SSQLS defined to hold the entire
+ row currently causes a segfault. To see this, use the stock.h
+ SSQLS definition in custom6. This is arguably a bug; see if we
+ can't make it just fill out the fields queried for, and leave
+ the rest unchanged.
o Add a configure script option to allow the new lock
mechanism to use platform mutexes via the Boost.Threads
@@ -156,6 +180,19 @@
the return from bitset::to_ulong() in an UNSIGNED INTEGER
column, and another for storing a larger set of bits in a
more flexible way, perhaps as a BLOB.
+
+ o Apply Waba's patch allowing Null<T> fields in SSQLSes:
+ http://lists.mysql.com/plusplus/5433
+
+ o Row object currently depends on the associated ResUse object
+ to stick around through all calls to .at(), because it needs
+ the list of field types in the result set to construct
+ ColData objects. This means it's not possible to store
+ the result of several queries before accessing the data.
+ Currently, this is just a documented limitation, but it
+ would be nice if there were a clean way to avoid this.
+ Obviously you could just copy the type list when constructing
+ the Row object, but that seems pointlessly inefficient.
o Define operator<< for Fields, Row, ResUse, etc. In other
words, there should be a way to get a user-readable version
@@ -275,15 +312,6 @@
These items could happen in any version.
- o Document restrictions on order of destruction. See this thread:
- http://lists.mysql.com/plusplus/5084
-
- o Storing a subset row in an SSQLS defined to hold the entire
- row currently causes a segfault. To see this, copy the SSQLS
- definition from custom1 to custom6. This is arguably a bug;
- see if we can't make it just fill out the fields queried for,
- and leave the rest unchanged.
-
o 64-bit integer support has been reported to work, but more
confirmation is wanted.
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
