[webkit-qt] setOfflineWebApplicationCacheQuota clears db

[Andrew Webster]

On Tue, Aug 3, 2010 at 11:01 AM,  <Chang.Shu at nokia.com> wrote:
> This behavior matches the other platforms. A workaround for you could be read the quota first before you reset it (if not big enough).

The quota always reads 0x7FFFFFFF until I set it.  I think that the
"PRAGMA max_page_count" that this uses is set per-connection, not
per-database, so it must be set every time.

Andrew

>
> Thanks
>
> Chang
>
> -----Original Message-----
> From: webkit-qt-bounces at lists.webkit.org [mailto:webkit-qt-bounces at lists.webkit.org] On Behalf Of ext Andrew Webster
> Sent: Tuesday, August 03, 2010 10:51 AM
> To: webkit-qt
> Subject: [webkit-qt] setOfflineWebApplicationCacheQuota clears db
>
> Ever since change 56140 in the svn trunk,
> QWebSettings::setOfflineWebApplicationCacheQuota clears out the
> application cache database before setting the maximum number of pages:
>
>  void QWebSettings::setOfflineWebApplicationCacheQuota(qint64 maximumSize)
>  {
>  #if ENABLE(OFFLINE_WEB_APPLICATIONS)
> +    WebCore::cacheStorage().empty();
> +    WebCore::cacheStorage().vacuumDatabaseFile();
>     WebCore::cacheStorage().setMaximumSize(maximumSize);
>  #endif
>  }
>
> I thought that the maximum number of pages in the database is a
> per-connection setting and thus needs to be set up every time an
> application starts (as opposed to only once when the database is
> created).  So, I used to call setOfflineWebApplicationCacheQuota at
> the start of my application, but that now clears the database.
>
> Is there a different way that I should be setting the maximum cache
> size, or am I misunderstanding what setOfflineWebApplicationCacheQuota
> is supposed to do?
>
>
> Thanks,
> Andrew Webster
> _______________________________________________
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>