- **status**: accepted --> duplicate
- **Comment**:
My mistake.
This ticket did not propose any change of column type or representation form,
only a change in the unpacking/reading/transformation from the existing
sqlite representation to the internal form.
But that is exactly a solution to the original ticket #53.
Closing this ticket as duplicate of #53
If there are ideas on how to improve performance for PBE loading and or
dumping then these are always welcome as new enhancement tickets/proposals.
---
** [tickets:#843] IMM: replace sqlite3_column_text in immload**
**Status:** duplicate
**Milestone:** 4.5.FC
**Created:** Wed Apr 09, 2014 02:07 PM UTC by Zoran Milinkovic
**Last Updated:** Thu Apr 10, 2014 08:24 AM UTC
**Owner:** Zoran Milinkovic
Today, sqlite3_column_text function is used for retrieving results of all data
types.
Retrieving results for double data type, floating-point precision is lost due
to string format of 15 digits in string result.
Depending on data type, sqlite3_column_text function should be replaced with
the corresponding sqlite3 function.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
