Still uses BROWSE.VC.DB even when rename option selected

[johnfredcee]

The DB files don't seem to be excessively large. Although I have the db name set to "databaseFilename" : "chunks.vs.db" - I have both that and a .BROWSE.VC.DB under my AppData\Roaming\Code\User\workspaceStorage\9579cac8ebcc1d93e3a73c892073cd93\ms-vscode.cpptools with modification times within a couple of minutes of the crash times.

[johnfredcee]

(This is on a small C project of just five files)

[bobbrow]

We should delete the old DB when databaseFilename changes

[johnfredcee]

It re-creates it.

…

On 14 March 2017 at 16:32, Bob Brown ***@***.***> wrote: We should delete the old DB when databaseFilename changes — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#558 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA18abggGylS6BKPbJgIyspeUmvjLq0ks5rlsEOgaJpZM4MboaR> .

-- ------------------------------------------- johnfredcee@googlemail.com

[sean-mcmanus]

I'm confused. Are you saying that both database files are being used and recreated after you delete them?

[johnfredcee]

Yes - the sequence of events is delete workspaceStorage, start you editor on a project with databaseFilename set somewhere else...after awhile (it can be as much as 20 mins) a new BROWSEDB in worspaceStorage seems to get created, even though the new db was created where you would expect (the databaseFilename setting) within a minute of startup.

[dkhelwig]

Having the same issue. I've set "databaseFilename": ".vscode/browse.db", closed VS code, deleted everything in ~/Library/Application Support/Code/User/workspaceStorage/ and then opened VS code. After a few seconds a new folder will be created within workspaceStorage with the following content.

-rw-r--r--  1 ---  ---  395255808 Apr  6 10:05 .browse.VC.db
-rw-r--r--  1 ---  ---      65536 Apr  6 10:04 .browse.VC.db-shm
-rw-r--r--  1 ---  ---   18107432 Apr  6 10:04 .browse.VC.db-wal

[sean-mcmanus]

Can you try using ${workspaceRoot}/.vsode/browse.db? I think ".vscode/browse.db" is an invalid path so it's falling back to the workspaceStorage.

[dkhelwig]

Hey that worked thank you. Could that please be added to the documentation on hover? Right now it incorrectly states:

Path to the generated symbol database. Empty string means default to rootfolder/.vscode/.browse.VC.db

[vscpp]

@sean-mcmanus , seems c_cpp_properties.json configure file only for current project (c_cpp_properties.json created in current project).

I want to modify databaseFilename setting for each project on my computer, may I know whether extension supports a global setting for databaseFilename? Which is means that if I open a new folder by VS code, the symbol will be created in my databaseFilename, I don't need to update c_cpp_properties.json every time.

Thanks.

[sean-mcmanus]

@vscpp We haven't implemented a user setting to change the default location yet. There's an issue on the VS Code side about adding a setting for the default storage location: microsoft/vscode#22557. We also have this issue for making the includePath per-user, which would also apply to the other settings: #368 .

[vscpp]

@sean-mcmanus, sorry, bother you again. :) I read the microsoft/vscode#22557, seems the requirement is changing default storage location from Temp to other drive. It's a global setting for all VS code related.
But I remember that C/C++ extension will create the symbols file in workspace .vscode folder with old version cpptool. Developer didn't need to update the c_cpp_properties.json file, it was automatic. That was a good idea.
But the design changed after one version released, it moved the symbols files to Temp folder.
May I know what's the reason for this change? Thanks.

(I introduced the VS code and C/C++ extension to my colleagues, and our project code size is very huge (6GB), so it will take a lot of space in C drive for symbols generation. They complain to me :( )