LinkedIn
Twitter
1 ACCEPTED SOLUTION
It sounds like you're concerned more about the memory used by the device rather than the storage used on your data source.
Does the user or the app access the uploaded images after the upload? If not, you could create a separate table to receive the uploads and configure the table to filter out all existing rows:
This would allow the uploads, but the app itself would never be aware of uploads that have already been performed.
An alternative would be to use a security filter on the upload table that omits older uploads, so the app only sees the more-recent uploads and/or the uploads the user is likely to need.
It sounds like you're concerned more about the memory used by the device rather than the storage used on your data source.
Does the user or the app access the uploaded images after the upload? If not, you could create a separate table to receive the uploads and configure the table to filter out all existing rows:
This would allow the uploads, but the app itself would never be aware of uploads that have already been performed.
An alternative would be to use a security filter on the upload table that omits older uploads, so the app only sees the more-recent uploads and/or the uploads the user is likely to need.
