Hi Warren,
After applying this patch, things look better now. But, I am seeing couple
of warning messages, when compiling examples/custom7.cpp, see below,
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../lib
-I/home/shanmugam/mysql/mysqlcom-5.0.64/include -g -O2 -MT custom7.o -MD
-MP -MF ".deps/custom7.Tpo" -c -o custom7.o custom7.cpp; \
then mv -f ".deps/custom7.Tpo" ".deps/custom7.Po"; else rm -f
".deps/custom7.Tpo"; exit 1; fi
../lib/coldata.h: In member function `Type
mysqlpp::ColData_Tmpl<Str>::conv(Type) const [with Type = mysqlpp::Date,
Str
= mysqlpp::const_string]':
../lib/coldata.h:334: instantiated from `mysqlpp::Null<T, B>
mysqlpp::ColData_Tmpl<Str>::get_null() const [with T = mysqlpp::Date, B =
mysqlpp::NullisNull, Str = mysqlpp::const_string]'
../lib/coldata.h:152: instantiated from `mysqlpp::Null<T, B>
mysqlpp::ColData_Tmpl<Str>::conv(mysqlpp::Null<T, B>) const [with T =
mysqlpp::Date, B = mysqlpp::NullisNull, Str = mysqlpp::const_string]'
../lib/null.h:270: instantiated from `std::ostream&
mysqlpp::operator<<(std::ostream&, const mysqlpp::Null<Type,
Behavior>&)
[with Type = mysqlpp::Date, Behavior = mysqlpp::NullisNull]'
custom7.cpp:125: instantiated from here
../lib/coldata.h:346: warning: choosing `
mysqlpp::mysql_convert<mysqlpp::Date>::operator mysqlpp::Date()' over `
mysqlpp::Date::Date(const Str&) [with Str =
mysqlpp::mysql_convert<mysqlpp::Date>]'
../lib/coldata.h:346: warning: for conversion from `
mysqlpp::mysql_convert<mysqlpp::Date>' to `mysqlpp::Date'
../lib/coldata.h:346: warning: because conversion sequence for the
argument
is better
Is it benign? and Is this fixed in any newer patches?
Thanks,
Mani.
-----Original Message-----
From: Warren Young [mailto:mysqlpp@stripped]
Sent: Wednesday, November 26, 2008 10:00 AM
To: plusplus@stripped
Subject: Re: Nulls in SSQLS in v2.0.7
On Nov 25, 2008, at 3:42 PM, Manikandan Shanmugam wrote:
> Is Null type supported in SSQLS in this version?
No. It was added in 3.0.0.
> Is there any patches which can be applied to fix this problem?
You can try this: http://lists.mysql.com/plusplus/5433
I believe it was made against 2.0.7. If it works for you, great, but
if not, we won't be able to help you.
There are more reasons to upgrade to MySQL++ 3.0 than just Nullable
SSQLS fields.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:
http://lists.mysql.com/plusplus?unsub=1
