Repository problems - outdated workspace

Hi,

It seems you are using a versioned repository, even though you say you are not (the error message you get when you try to delete a folder says your repository is versioned).

If you are connecting to a versioned repository, you should create a repository connection that reflects this. That would enable you to update your local workspace, which is what you need to do when your local items are outdated.

Versioned folders can not be deleted. CVS doesn't support this, and BVS uses the folder as the location of versioning history for the items contained in the folder.

Regards,

Jostein

Hi Jostein,

I'm a little confused with that error message. I was almost certain to have created a "no versioning or shared workspace" repository, and I don't see a local copy of the workspace in the filesystem (or I could not recognize one).

I've been able to Check In/ Checkout items from the repository all along, but no other options from the Versioning menu (like Promote version for example). This made sense to me, the checkin/checkout as a mechanism of controlling access to a shared workspace.

I've been working like this for more than a month now, and I'm still able to checkin/checkout all other items. Just not this particular one.

I've tried connecting to the repo as suggested and I get "Shared workspace Blaze Versioning does not support update API with entry path as the argument.".

Is there a simple way to check what kind of repo I've created?

Thanks for your help,

Jorge

Sorry about that, I was confusing conection types with repository types.

Therefore I believe the repository type I've created was Database Repository (BVS versioning shared).

Well, if a refresh doesn't work it is difficult to say. It could also be a bug - for example that there is a difference between the information in the entity descriptor ("innovator attributes" file) and the versioning information. If that is the case, you might need to fix it manually (more difficult with a database repository than with a file system, but possible I think).

Regards,

Jostein

Thanks for your help. I'll try that.

Regards, Jorge

Hi Jorge,

Did you be able to solve this problem. I also suffer the same at the moment.

I appreciate any hints

Goerkem

it comes down to what Jostein mentioned earlier. (http://discuss.fico.com/../user/viewprofilepage/user-id/89)

say the ruleset name is abc and there are versions 1,2, and 3

if you go to the instance file of abc and compare it with the _Attic file abc_3

they should match. still in the _Attic there should be an abc_version_info.xml.

make sure the last entry in there is version 3.

hopefully that clears things up.

I am a bit new to topic and trying to understand.

I have a database repository for the project and in database I see all the instances are just saved in the same table.

Where do I find this file to compare it? Is it also in the database?

How can I solve the problem efficiently. delete all the relevant instances in the database and check in the project again?

i'm not sure about the database repository but you can export it to a file base project, make your changes, and then convert it back to a database repo.