Saving creates new database file instead of overwriting the old one

[TLCFEM]

It seems that the new version 3.8.2 changes the saving manner. The old versions just overwrite the original file. I guess the new version rename the orginal file to the backup file and write a new database file.

This causes trouble for me (maybe also for others). I use hard links to point to the same database file in different folders so that the database can be updated automatically.

Currently the orginal file is either deleted or renamed. Hence the link is broken.

Will the developers consider to change it back to original saving manner?

[koppor]

Refs #2635

[TLCFEM]

I'd like to kindly comment that I am using Windows 7 so...

[stefan-kolb]

@JabRef/developers Is this still valid for 4.0? Will we change this?

[TLCFEM]

As far as I can tell, in 4.0 beta 3 the problem still exist..

[koppor]

@TLCFEM You say, that 3.8.1 worked correctly or some other earlier version?

[TLCFEM]

It has been a long time and I cannot remember exactly. So far I can tell that version 3.6 works properly so the modification was carried out somewhere between version 3.6 and 3.8.2. And I am sure that there is no fix since 3.8.2. I know little about Java so I cannot examine the codes and locate the problem. Sorry for little information provided.

[tobiasdiez]

So your final aim is to include one bib file in many tex documents without having to copy the file over and over again? For this, TeX actually provides a neat mechanism: you can put your bib file in a central folder (or register the current location within your TeX distribution), where every TeX document find it. See for example the following answer to a similar question.

[koppor]

Solution for a potential developer: Check our file mode when writing. It should truncate + append, not delete and recreate.