Replacing a line in a file

Question

Hi
I am trying to find a way to:

1. Edit Data
2. Delete Data

From a file using c#
I read up online and it seems everyone's solution is to rewrite or either recreate the file without the wanted information but I doubt that is the most efficient way...and for what I'm trying to do that just wont work.

Example.
I have a text file with the following Lines
1. TEST2
2. TEST2
3. TEST3

If I want to replace Line 2 with TEST8 it's easy by using

byte[] bytes = Encoding.UTF8.GetBytes(Environment.NewLine + "TEST8" + Environment.NewLine);
fs.Seek(XXX,SeekOrigin.Current);
fs.Write(bytes, 0, bytes.Length);
fs.Close();

But if I want to
replace it with "Testing123" it will start overriding the bytes of line 3.

Is there any way it can be done ? can I move the remaining bytes to the right to avoid the override ?
Or is there a easier way to do this ?

Also I would is I would like to completely Delete a line from the file.

Thx
Rousseau

Sam Hobbs · Answer

Yes padding would certainly make the file larger but you asked for the  most efficient way  snd you did not define efficiency. Note that you can improve both time and space efficiency using one of the other techniques I described.

Rousseau Sennett · Answer

Using padding seemed like the easiest idea but then I found the following class http://www.codeproject.com/KB/cs/InsertTextInCSharp.aspx which gave me the info I needed to move my bytes around in the file... because padding would have made my file larger... although I doubt that would really have mattered... anyway all I did was write my own Method to this class for deleting bytes by just moving all the bytes to the right of my position to the left for the amount of bytes I want to delete and setting the file length to Length – Number of bytes Deleted. Also this class includes a Method Find() which displayed some weird behaviour I didn't really go through the code to find out why the find method behaved like this was just easier to write my own But when I used ex. 12345 > And Ran Find( >) it would return position 5; And if I change the text to. > > And ran Find( >) it would return 4;

Sam Hobbs · Answer

Imagine you have a wall made of bricks and you want to replace a brick with one that is longer but you don't want to break any bricks. How are you going to do that? You must either break a brick or move all the other bricks over. This is the type of thing that a database is good at; they are designed to allow efficient update of data. One way to do it is to design your file such that it has padding among the records. The application could be designed so that it ignores the padding when reading and it could go past the padding when writing data so that the padding is retained. If however new data exceeds the space occupied by data being replaced then the padding could be over-written and that would eliminate the need to re-write all data. The filw would need periodic maintenance to ensure that there is a sufficient amount of padding. Another way is to have a list of offsets into the file and the list could be ordered in the order that the records are supposed to be ordered in. Then the new data could be put anywhere and only the list of offsets needs to be updated. For example in your test data the first record would occupy either 5 or 7 bytes depending on whether the data included end-of-line bytes; let's say 5 bytes (no end-of-line bytes). So the second record would be at offset 5. A new record could be added at the end (offset 15) and then the list of offsets would be: 0 15 10

Vulpes · Answer

You can use the FileStream.SetLength() method to increase the file size by 'n' bytes. It's then a matter of moving all the bytes in the file after the insertion point 'n' bytes to the right and making the insertion at the appropriate place. Similarly you can delete a line (say 'n' bytes long) by moving all the bytes in the file immediately following it 'n' bytes to the left and then calling FileStream.SetLength() to truncate the file size by 'n' bytes. See http://msdn.microsoft.com/en-us/library/system.io.filestream.setlength.aspx