[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] to fix a compile error of merge-tracking on Windows

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2006-07-23 16:25:56 CEST

Masaru Tsuchiyama wrote:
> Index: subversion/libsvn_fs_fs/tree.c
> ===================================================================
> --- subversion/libsvn_fs_fs/tree.c (revision 20833)
> +++ subversion/libsvn_fs_fs/tree.c (working copy)
> @@ -1102,7 +1102,7 @@
> apr_pool_t *pool)
> {
> sqlite3_stmt *stmt;
> - long long int lastchanged_rev;
> + apr_int64_t lastchanged_rev;
> int sqlite_result;
>
> SQLITE_ERR(sqlite3_prepare(db, "SELECT MAX(revision) from mergeinfo_changed"
> @@ -1228,7 +1228,7 @@
> apr_hash_t *cacheresult;
> sqlite3_stmt *stmt;
> int sqlite_result;
> - long long int count;
> + apr_int64_t count;
> svn_boolean_t has_no_mergeinfo = FALSE;
>
> cacheresult = apr_hash_get(cache, path, APR_HASH_KEY_STRING);
>

Now I see we're using sqlite in fsfs. Interesting.
http://www.sqlite.org/lockingv3.html states explicitly that sqlite
databases aren't stable over NFS. Doesn't that somehow subvert the whole
idea point of using fsfs in the first place?

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 23 16:26:18 2006

This is an archived mail posted to the Subversion Dev mailing list.