On Mon, 28 Jan 2013 08:58:05 -0800 Pawel Aleksander Fedorynski <[email protected]> wrote:
PAF> So am I getting this right: what you essentially need is the ability to PAF> override the field type provided by the database engine (double in this PAF> case) with one provided by the user (which would be probably string here.) PAF> Is that correct? Hello, I think this might be too generic. IMHO just retrieving anything as string (i.e. in its textual raw form) should be fine. PAF> I may be wrong, but I don't think soci has such feature yet (others please PAF> correct me if that's wrong.) I see no reason why it couldn't be PAF> implemented, though it may be not entirely trivial. This is the first time PAF> I think anyone needed such feature. It could have been useful for me when I was struggling by reading 64 bit integers from Oracle database via ODBC (Oracle ODBC is known to be broken and advertises support for SQL_BIGINT without really supporting it) but I already solved this inside SOCI in b82364e which is arguably even better. Still, being able to read the raw result would have allowed me to fix this faster. So I think the ability to retrieve textual representation from the database would be useful, as we already know of 2 different situations when it could be helpful. Regards, VZ
pgp0WNuhxURNX.pgp
Description: PGP signature
------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d
_______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
