Jul 6, 2009 at 11:02 PM
Edited Jul 6, 2009 at 11:40 PM
I've been reading through the source code so I should have a better idea of whats going on soon.
When adding a row is the number of records the last thing that gets updated? If this is the case, then if the software falls over before updating the record count then we would only use this record. It would be overwritten on the next insert...
However, what happens if the program crashed after updating only 1, 2 or 3 bytes of the 4 byte record count? You'd have to be pretty unlucky to end up with this sort of curruption, but it could happen.
Could this be an issue with any other fields?
One other thing I noticed was that after adding 500k rows, the application took about 3 seconds to close. Does this mean all these records were still in memory and had to be saved? If caching was disabled for write operations, is performance significantly
affected? Could you have caching for reads but not writes?
I would be happy to help with the project where I can.
On 500k rows, no indexes, the following takes 5 seconds:
=> x.dob <
string number = result.Count<Individual>().ToString();