(html5) Web SQL Storage Limitations in Chrome and Android?

[Matty-p]

So I am writing a web app that needs to store ~40MB of offline data in
a offline Web SQL database. It needs to work in Chrome (desktop),
Safari (desktop and mobile) and android's browser. Now I know that Web
SQL is supported in these browsers and I know since which versions but
i need to know how much storage is allowed. Safari desktop supports
500MB of database storage. Safari mobile supports 50MB of database
storage.

However I have spent literally hours searching everywhere to find out
what space chrome desktop supports and what the android browser
supports but cannot find anything concrete. One place noted a hard 5MB
limit for chrome desktop while another quoted a 25MB limit for chrome
desktop (without using a chrome extension). One source for android's
browser noted a 15MB limit another noted a 5MB limit. Can anyone point
me to somewhere that states what the actual hard limits on Web SQL
storage are for android and chrome??

[Eric Uhrhane]

I can't help you with Android, but have you looked at the Quota API?

https://developers.google.com/chrome/whitepapers/storage#managing_quota
http://updates.html5rocks.com/2011/11/Quota-Management-API-Fast-Facts

> --
> You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
> To post to this group, send email to chromiu...@chromium.org.
> To unsubscribe from this group, send email to chromium-html...@chromium.org.
> For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-html5/?hl=en.
>

[Mikhail Naganov]

Hi Matty,

I did a little research in the beginning of 2012, and this is how it
was working at that moment:

- there are 2 types of storage in HTML5: Temporary and Permanent

- Temporary storage can be used w/o any user permission;
- per-site quota size depends on free disk space size, on Nexus S
it was about 10Mb, on a 16Gb Galaxy Nexus the quota size was about
130Mb;
- the difference is because on Galaxy the entire flash memory is
available to applications, while on S only 1Gb of it;
- any attempts to query more space were silently truncated;

- to use Permanent storage, your application needs to get user's
permission; at the time I was testing it, WebSQL didn't support this
type of storage;
- for the permanent storage, it was possible to query up to 1Gb for
a site;