I will.
but please could you give me the instructions for contributing?
Best regards,
Sylvain
On Fri, Dec 24, 2010 at 2:14 AM, Mateusz Loskot <[email protected]> wrote:
> On 23/12/10 08:36, Sylvain Pointeau wrote:
> >
> > Is there a reason to use only sqlite3_column_text?
> > why don't you call as well:
> > sqlite3_column_double
> > sqlite3_column_int
> > sqlite3_column_int64
>
> I don't know. I'm not the author of the backend, so I can't tell what
> was the reason.
>
> > is it not a performance loss doing the conversion from text to any type?
>
> In theory, there may be some performance loss because for every non-text
> values, sqlite3_column_text call makes conversion
> from the actual (int,double, etc.) type to text.
> Then, SOCI reverts it. Though, I haven't measured it.
>
> I think it wouldn't hurt to replace the conversions with use of SQLite3
> API calls corresponding to SOCI x_* types in this function:
>
> sqlite3_standard_into_type_backend::post_fetch
>
> If you would be willing to give it a try, I say big thanks and
> patches are very welcome!
>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> Charter Member of OSGeo, http://osgeo.org
> Member of ACCU, http://accu.org
>
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
