If `.svn/format` exists, then read the number in it:

 - Version 7 is SVN 1.3
 - Version 8 is SVN 1.4
 - Version 9 is SVN 1.5

If `.svn/format` doesn&#39;t exist then the version number is on the first line in `.svn/entries`:

 - Version 10 is SVN 1.6
 - Version 12 is SVN 1.7

Subversion 1.6 was the first one not to use `.svn/format`. Version 7 and older used XML-based `.svn/entries` file, newer versions use less verbose line-based file format.

Since Subversion 1.7 the version number is stored in the `.svn/wc.db` SQLite database in the &quot;user_version&quot; field. So even though `.svn/format` is bumped to version 12 the actual format version is 29 and future versions may not update `.svn/format` anymore.  To obtain the version number from `.svn/wc.db` there are two methods:

 1. if you have `sqlite3` in your path, `sqlite3 .svn/wc.db &quot;PRAGMA user_version&quot;`
 2. if you DO NOT have `sqlite3` in your path, open `.svn/wc.db` in a hex editor and read the DWORD at offset 0x3c

All the format version numbers are described in [wc.h][1] along with the version numbers of respective Subversion releases.


  [1]: http://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_wc/wc.h

From Stack Overflow question *[Find out SVN working copy version (1.7 or 1.8)][1]*: 

One can use `sqlite3 .svn/wc.db &quot;PRAGMA user_version&quot;` on SVN 1.7 or later (or `od -An -j63 -N1 -t dC .svn/wc.db` if you only have the [SQLite 3.0][2] libraries, YMMV).

  [1]: https://stackoverflow.com/questions/19265363
  [2]: https://en.wikipedia.org/wiki/SQLite#History


Performance question ...

I have a database of houses that have geolocation data (longitude &amp; latitude).

What I want to do is find the best way to store the locational data in my MySQL (v5.0.24a) using InnoDB database-engine so that I can perform a lot of queries where I&#39;m returning all the home records that are between x1 and x2 `latitude` and y1 and y2 `longitude`.

Right now, my database schema is

    ---------------------
    Homes   
    ---------------------
    geolat - Float (10,6)
    geolng - Float (10,6)
    ---------------------

And my query is:

    SELECT ... 
    WHERE geolat BETWEEN x1 AND x2
    AND geolng BETWEEN y1 AND y2

 - Is what I described above the best way to store the
   latitude and longitude data in MySQL using Float (10,6) and separating out the longitude/latitude? If not, what is? There exist Float, Decimal and even Spatial as a data type.
 - Is this the best way to perform the
   SQL from a performance standpoint? If not, what is?
 - Does using a different MySQL
   database-engine make sense?

**UPDATE: Still Unanswered**

I have 3 different answers below. One person say to use `Float`. One person says to use `INT`. One person says to use `Spatial`.

So I used MySQL &quot;EXPLAIN&quot; statement to measure the SQL execution speed. It appears that absolutely no difference in SQL execution (result set fetching) exist if using `INT` or `FLOAT` for the longitude and latitude data type..

It also appears that using the &quot;`BETWEEN`&quot; statement is SIGNIFICANTLY faster than using the &quot;`&gt;`&quot; or &quot;`&lt;`&quot; SQL statements. It&#39;s nearly 3x faster to use &quot;`BETWEEN`&quot; than to use the &quot;`&gt;`&quot; and &quot;`&lt;`&quot; statement.

With that being said, I still am unceratin on what the performance impact would be if using Spatial since it&#39;s unclear to me if it&#39;s supported with my version of MySQL running (v5.0.24) ... as well as how I enable it if supported.

**Any help would be greatly appreacited**



Database/SQL: How to store longitude/latitude data?

I was trying to make my own class for currencies using longs, but apparently I should use `BigDecimal` instead. Could someone help me get started? What would be the best way to use `BigDecimal`s for dollar currencies, like making it at least but no more than 2 decimal places for the cents, etc. The API for `BigDecimal` is huge, and I don&#39;t know which methods to use. Also, `BigDecimal` has better precision, but isn&#39;t that all lost if it passes through a `double`? if I do new `BigDecimal(24.99)`, how will it be different than using a `double`? Or should I use the constructor that uses a `String` instead?

Using BigDecimal to work with currencies

For example, the SVN 1.5 client has one layout for working copies, and the SVN 1.6 client has a different layout. I understand that the layout automatically gets upgraded when it gets touched by a newer client.

If I have a working copy on my system, how can I find out the version of the layout it&#39;s using?


How do I determine the SVN working copy layout version?

<p>For example, the SVN 1.5 client has one layout for working copies, and the SVN 1.6 client has a different layout. I understand that the layout automatically gets upgraded when it gets touched by a newer client.</p>
<p>If I have a working copy on my system, how can I find out the version of the layout it's using?</p>


I deleted manually a directory I just added, offline, in my repository. I can&#39;t restore the directory.

Any attempt to do an update or a commit will fail with: 

    &quot;blabla/.svn&quot; containing working copy admin area is missing.

I understand why, but is there anyway to fix this.

I don&#39;t want to checkout the entire repo and add my changes to it manually, it would take hours.

How to fix &quot;containing working copy admin area is missing&quot; in SVN?

So - I used to have a directory called mysql a few revisions ago.  I deleted it, and decided to start over - but when I try to create the new mysql directory - I keep running into the &#39;File Already Exists&#39; error:

    support:/etc/puppet/modules# mkdir mysql
    support:/etc/puppet/modules# svn add mysql/
    A         mysql
    support:/etc/puppet/modules# svn commit -m &quot; Test&quot;
    Adding         modules/mysql
    svn: Commit failed (details follow):
    svn: File already exists: filesystem &#39;/var/lib/svn/puppet/db&#39;, transaction &#39;11-r&#39;, path &#39;/trunk/modules/mysql&#39;
    support:/etc/puppet/modules# svn delete mysql
    svn: Use --force to override this restriction
    svn: &#39;mysql&#39; has local modifications
    support:/etc/puppet/modules# svn --force delete mysql
    D         mysql

I saw some other posts suggest forcing an update

    support:/etc/puppet/modules# svn status
    support:/etc/puppet/modules# svn update
    At revision 11.
    support:/etc/puppet/modules# svn mkdir mysql
    A         mysql
    support:/etc/puppet/modules# svn commit -m &quot;Test&quot;
    Adding         modules/mysql
    svn: Commit failed (details follow):
    svn: File already exists: filesystem &#39;/var/lib/svn/puppet/db&#39;, transaction &#39;11-s&#39;, path &#39;/trunk/modules/mysql&#39;



Strange problem with Subversion - &quot;File already exists&quot; when trying to recreate a directory that USED to be in my repository

I was reading a blog where the writer said this  

&gt; **&quot;Code doesn’t exist unless it’s checked into a version control system. Use version control for everything you do. Any version control, SVN, Git, even CVS, master it and use it.&quot;**  

I have never used any sort of version control and I do not find it that great. I have googled it and looked at it before, but I just need it put into children&#39;s terms if you will please.  

As I understand it right now, things like SVN are for storing your code online for a group of users or other developers to have access to the same code. Once you update some code, you can submit the new version and the SVN will keep copies of old code as well as the new ones you update.  

Is this the basic idea of it or am I getting it completely wrong?  

If I am right, then it might not be much use if I:

 - Do not have other people working on the code.
 - Do not plan on letting others have the code.


  [1]: http://stackoverflow.com/questions/250984/do-i-really-need-version-control

Why should I use version control?

I want to checkout a specific revision of a folder in [Subversion][1] using the command line.

I don&#39;t see an option for specifying the revision number in `TortoiseProc.exe`,

    TortoiseProc.exe /command:checkout &lt;url&gt;

How do I get the revision I want? Is `TortoiseProc.exe` the right tool for what I want to do?

  [1]: http://en.wikipedia.org/wiki/Apache_Subversion


How to checkout a specific Subversion revision from the command line?

Assume that you have a directory under subversion control, that contains some files and tons of subdirectories, like that:

    file1.txt
    file2.txt
    file3.txt
    dir1/
    dir2/
    dir3/
    dir4/
    :
    dirXX/

Now you need the files and some of the dirs, but not all of them. This can be done with SVN. Just make the checkout non-recursive:

    svn checkout -N &lt;URL&gt;

This checks out only the first directory and the files inside. No subdirectories are included. Even if you go into the checkout directory and run a &quot;`svn up`&quot;, it will only update the files checked out previously, it will not add the directories. You can now selectively add the directories you need by explicitly updating those. E.g. if you need dir2 and dir4 only, you can go into the checkout directory and execute

    svn up dir2
    svn up dir4

If you run a generic &quot;`svn up`&quot; in the future, it will only update the files and those two directories, it will not add any of the other directories.

Now the problem: What if I decide at any later point that I don&#39;t need dir2 any longer? How do I get rid of it? There seems no way of doing so, other than deleting the whole checkout and start over from scratch.

When you just delete dir2, the next &quot;`svn up`&quot; will bring it back, as &quot;`svn status`&quot; of course shows it as missing now (&quot;!&quot; in front of its name). Running a &quot;`svn remove`&quot; will remove it of course, but on next commit it will also remove it from the repository, which must not happen.

Even the new sparse directory (&quot;shallow checkout&quot;) feature of SVN 1.5 is of no use here:

&gt; Subversion 1.5&#39;s implementation of
&gt; shallow checkouts is good but does not
&gt; support a couple of interesting
&gt; behaviors. First, you cannot
&gt; de-telescope a working copy item.
&gt; Running svn update --set-depth empty
&gt; in an infinite-depth working copy will
&gt; not have the effect of discarding
&gt; everything but the topmost
&gt; directory—it will simply error out.
&gt;&lt;br&gt; - [http://svnbook.red-bean.com/en/1.5/svn.advanced.sparsedirs.html][1]

Is this complete impossible with SVN? Anyone ever came up with a clever work-a-round to that?

Just creating the checkout directory (without SVN) and then checking out the individual subdirectories from the repository directly as subdirectories to this directory will work for the directories: now every directory is a checkout of its own, can be updated and once not needed any longer, you can just delete it. However, how do I get the files then (e.g. file1.txt)? SVN does not allow to checkout individual files, you can only checkout whole directories.

  [1]: http://svnbook.red-bean.com/en/1.5/svn.advanced.sparsedirs.html

SVN: Can you remove directories from a local checkout only (not from the repository)?

I would like to remove all changes to my working copy.&lt;br /&gt;
Running `git status` shows files modified.&lt;br /&gt;
Nothing I do seems to remove these modifications.&lt;br /&gt;
E.g.:&lt;br /&gt;

    rbellamy@PROMETHEUS /d/Development/rhino-etl (master)
    $ git status
    # On branch master
    # Changed but not updated:
    #   (use &quot;git add &lt;file&gt;...&quot; to update what will be committed)
    #   (use &quot;git checkout -- &lt;file&gt;...&quot; to discard changes in working directory)
    #
    #       modified:   Rhino.Etl.Core/Enumerables/CachingEnumerable.cs
    #       modified:   Rhino.Etl.Core/Pipelines/SingleThreadedPipelineExecuter.cs
    #       modified:   Rhino.Etl.Tests/Rhino.Etl.Tests.csproj
    #       modified:   Rhino.Etl.Tests/SingleThreadedPipelineExecuterTest.cs
    #
    no changes added to commit (use &quot;git add&quot; and/or &quot;git commit -a&quot;)
    
    rbellamy@PROMETHEUS /d/Development/rhino-etl (master)
    $ git checkout -- Rhino.Etl.Core/Enumerables/CachingEnumerable.cs
    
    rbellamy@PROMETHEUS /d/Development/rhino-etl (master)
    $ git status
    # On branch master
    # Changed but not updated:
    #   (use &quot;git add &lt;file&gt;...&quot; to update what will be committed)
    #   (use &quot;git checkout -- &lt;file&gt;...&quot; to discard changes in working directory)
    #
    #       modified:   Rhino.Etl.Core/Enumerables/CachingEnumerable.cs
    #       modified:   Rhino.Etl.Core/Pipelines/SingleThreadedPipelineExecuter.cs
    #       modified:   Rhino.Etl.Tests/Rhino.Etl.Tests.csproj
    #       modified:   Rhino.Etl.Tests/SingleThreadedPipelineExecuterTest.cs
    #
    no changes added to commit (use &quot;git add&quot; and/or &quot;git commit -a&quot;)
    
    rbellamy@PROMETHEUS /d/Development/rhino-etl (master)
    $ git checkout `git ls-files -m`
    
    rbellamy@PROMETHEUS /d/Development/rhino-etl (master)
    $ git status
    # On branch master
    # Changed but not updated:
    #   (use &quot;git add &lt;file&gt;...&quot; to update what will be committed)
    #   (use &quot;git checkout -- &lt;file&gt;...&quot; to discard changes in working directory)
    #
    #       modified:   Rhino.Etl.Core/Enumerables/CachingEnumerable.cs
    #       modified:   Rhino.Etl.Core/Pipelines/SingleThreadedPipelineExecuter.cs
    #       modified:   Rhino.Etl.Tests/Rhino.Etl.Tests.csproj
    #       modified:   Rhino.Etl.Tests/SingleThreadedPipelineExecuterTest.cs
    #
    no changes added to commit (use &quot;git add&quot; and/or &quot;git commit -a&quot;)
    
    rbellamy@PROMETHEUS /d/Development/rhino-etl (master)
    $ git reset --hard HEAD
    HEAD is now at 6c857e7 boo libraries updated to 2.0.9.2 and rhino.dsl.dll updated.
    
    rbellamy@PROMETHEUS /d/Development/rhino-etl (master)
    $ git status
    # On branch master
    # Changed but not updated:
    #   (use &quot;git add &lt;file&gt;...&quot; to update what will be committed)
    #   (use &quot;git checkout -- &lt;file&gt;...&quot; to discard changes in working directory)
    #
    #       modified:   Rhino.Etl.Core/Enumerables/CachingEnumerable.cs
    #       modified:   Rhino.Etl.Core/Pipelines/SingleThreadedPipelineExecuter.cs
    #       modified:   Rhino.Etl.Tests/Rhino.Etl.Tests.csproj
    #       modified:   Rhino.Etl.Tests/SingleThreadedPipelineExecuterTest.cs
    #
    no changes added to commit (use &quot;git add&quot; and/or &quot;git commit -a&quot;)

git status shows modifications, git checkout -- &lt;file&gt; doesn&#39;t remove them

I&#39;ve got a SVN Repository that has moved to a new address/path. However, I&#39;ve got a working copy with uncommitted source code still pointing to the old (now invalid) repository path. How do you change a working copy to point at a new repository?

SVN - Change working copy to point at new svn path

When cloning a repository with mercurial you can pass the -U/--noupdate flag to create a clone with no working copy. Can I remove the working copy if I forget to pass this flag at clone time? And if so, how?

This is conceptually similar to [this git question](https://stackoverflow.com/questions/2199897/git-convert-normal-to-bare-repository), but for mercurial.

How can I remove the working copy from a Mercurial clone?

I cannot do a SVN commit. I get this error:

    org.apache.subversion.javahl.ClientException: The working copy needs to be upgraded
    svn: Working copy &#39;C:\.... is too old (format 10, created by Subversion 1.6)

How can it be fixed?

SVN upgrade working copy

How can I diff my current working copy against a stash?

My use case: my working copy already contains a subset of the changes in my `stash@{0}`, but I don&#39;t want to apply _all_ the changes in `stash@{0}`. I want to do a diff to help determine which desirable changes in `stash@{0}` are still missing from my working copy.

Content Type	Original Author	Original Content on Stackoverflow
Question	William Leara	View Question on Stackoverflow
Solution 1 - Svn	Filip Navara	View Answer on Stackoverflow
Solution 2 - Svn	user3090766	View Answer on Stackoverflow

How do I determine the SVN working copy layout version?

Svn Problem Overview

Svn Solutions

Solution 1 - Svn

Solution 2 - Svn

Using BigDecimal to work with currencies

Database/SQL: How to store longitude/latitude data?

Attributions