Since 1.8.8 (?) you can call "svn upgrade" to add that table. Optimizer results) when the WC database is opened, if the table doesn'tĪlready exist. We'll now create the SQLite stats table (that improves the query Performance issues: in 1.9 and trunk (and the proposed 1.8 backport), Just to clarify, since Marc actually knows something about one of the For 1.9 it is accepted for backport, but for 1.8 it misses a final vote. > The performance fix is nominated for both 1.9 and 1.8. > And it looks like both 1.9 and a future 1.8 will improve performance on working copies initially created/upgraded with 1.8.0-1.8.7, but not already explicit 'svn upgrade'-d with a later version, when it internally uses Sqlite 3.8 or later. Is that correct > There are no schema changes, but 1.9 is faster at many working copy > operations due to more optimized queries. SVNKit 1.10.10 is compatible both with Subversion 1.10, 1.9, 1.8 and Subversion 1.7 working copy formats. Anyway, because it only runs on Windows it is arguably more tightly integrated. VisualSVN Server only runs on Windows servers, which is not an issue if that is what you want to use. > Currently it looks like you don't need to call svn upgrade. changes in the release notes, Subversion 1.9 seems to be backwards > compatible with Subversion 1.8 working copies. All three are free, but only SVN Edge is open-source. The SVNKit client library (formerly known as JavaSVN) is a 100 pure Java implementation, and attempts to track the latest changes to Subversion's core libraries however, this is an independent project and the Subversion project cannot make any promises as to its compatibility with the official Subversion implementation. > As 1.9 is not final yet we can't definitely answer that. > Does that mean than an "svn upgrade" should still be invoked to get > operations due to more optimized queries. > There are no schema changes, but 1.9 is faster at many working copy > compatible with Subversion 1.8 working copies. > changes in the release notes, Subversion 1.9 seems to be backwards > From my experiments with Subversion 1.9 binaries and the listed Mendix Studio Pro has a (built-in) Subversion client that uses version 1.9 of the SVN working copy format. This client should be compatible with any 1.x version of the SVN server, so you could use, for example, a 1.6.x or 1.9.x SVN server as well. > On 16:34, Branko Čibej wrote:> On 15:58, Marc Mendix Studio Pro uses the Subversion 1.9 working copy. Subject: Re: Subversion 1.9 working copy compatibility
0 Comments
Leave a Reply. |