Allow concurrent check out

[GoogleCodeExporter]

Hi,

Can you please add support for concurrent check out?
Even partial implementation, where I can just CO, without option to check back 
in, will be better than no CO at all.

I need this because our application object has a hard-coded line which we need 
to change often to switch between DBs, when developing. If the object is not 
CO, it can't be edited.

Original issue reported on code.google.com by GevaZeic...@gmail.com on 14 Feb 2011 at 12:50

[GoogleCodeExporter]

Forgot to label it with a "Suggestion:".. sorry :)

Original comment by GevaZeic...@gmail.com on 14 Feb 2011 at 12:52

[GoogleCodeExporter]

Can you tell me a use-case for that.
I mean why do you need do a check-out without check-in?
--
Regards,
  Dmitry

Original comment by daggett....@gmail.com on 14 Feb 2011 at 5:59

[GoogleCodeExporter]

Because of that application object. There's code there that I need to change in 
order to run the project from the IDE, on a different database. This object can 
only be edited and saved, after check-out. I don't need to check it back in - 
the changes are always temporary.
Without concurrent CO, only one developer at a time can have the object checked 
out. We wish to keep the object checked out on all the developers' machines.
If there was a way to write to the object without CO, it would be a good 
alternative.

Original comment by GevaZeic...@gmail.com on 15 Feb 2011 at 6:32

[GoogleCodeExporter]

To edit temporarily without a checkout you could use a "scratch" library at the 
top of your library list. Do a "save as" of your application object to the 
scratch library and you can then edit it as required. If you never add new 
objects in your scratch library to source-control no other developers will be 
affected.

Original comment by stuart.m...@gmail.com on 25 Oct 2011 at 8:42