[TIMOB-3393] DB Get API extended to support typed return value
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | Trivial |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-18T16:42:12.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.7.0, Sprint 2011-15 |
| Components | iOS |
| Labels | feature, ios, release-1.7.0 |
| Reporter | Reggie Seagraves |
| Assignee | Jacob Relkin |
| Created | 2011-04-15T03:43:41.000+0000 |
| Updated | 2017-03-08T00:43:00.000+0000 |
Not enough information is provided.
See #3519.
If a ticket needs more information. You need to set its state to needs-more-info and assign it to the person who needs to provide the info. Otherwise, it'll fall through the cracks.
Scheduling this to coincide with the Android work, moving to Sprint 15.
Pushing into Sprint 16 for resource leveling.
(from [2fa2355a24d044e4d21830ddbdb3dc9ee4986643]) [#3393 state:fixed-in-qa] Added support for typed return values for column getters to TiDatabaseResultSetProxy. https://github.com/appcelerator/titanium_mobile/commit/2fa2355a24d044e4d21830ddbdb3dc9ee4986643"> https://github.com/appcelerator/titanium_mobile/commit/2fa2355a24d0...
(from [ce793436c38f3f6c2e93b74e85c0d65568d3fab9]) [#3393] iOS implementation, Drillbit tests and API documentation are done. getFloat() has some precision loss somewhere along the way to JS land and causes one test to fail. We should think about a) why this is happening and b) if we really need getFloat() in the first place. https://github.com/appcelerator/titanium_mobile/commit/ce793436c38f3f6c2e93b74e85c0d65568d3fab9"> https://github.com/appcelerator/titanium_mobile/commit/ce793436c38f...
Is this really resolved? After the changes that Don made to the DB API + drillbit tests, the new API needs to be implemented on iOS. I think this issue should be merged with TIMOB-3519.
Closing ticket as resolved.