Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate avoiding fetch of media info record (_bn) #771

Closed
mitchellsundt opened this issue Jul 9, 2015 · 1 comment
Closed

Investigate avoiding fetch of media info record (_bn) #771

mitchellsundt opened this issue Jul 9, 2015 · 1 comment

Comments

@mitchellsundt
Copy link
Contributor

mitchellsundt commented Jul 9, 2015

Migrated to getodk/aggregate#42 by spacetelescope/github-issues-import

Originally reported on Google Code with ID 770

Can we avoid fetching any of the _bn records for the submissions data page?

I think we can construct the URL for the media without knowing this info. And we know
the media type from the form definition, so we know what treatment to do without getting
the exact contentType.

This would allow ODK Scan surveys to be presented/hosted in AppEngine and not hit the
60-second limit.

We would then only do explicit reads when accessing the media files, the form definition's
media list, and never when accessing the submission rows.


Reported by mitchellsundt on 2013-02-19 19:46:52

@mitchellsundt
Copy link
Contributor Author

mitchellsundt commented Jul 9, 2015

Migrated to opendatakit/aggregate#42 (comment) by spacetelescope/github-issues-import

Unfortunately, this would not allow null (missing media) to be reported directly. Instead,
a link would always be constructed which may or may not have any data.

The only work-around would be to change the data representation of a submission to
have a flag in the parent record indicating whether or not there was data in the _bn
table for this record. 

We could do the same optimization for the multiple-choice entries as well.

Reported by mitchellsundt on 2013-03-15 00:11:56

  • Labels added: 2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants