View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001187 | JEDI VCS | Server | public | 2003-10-17 02:11 | 2005-06-13 16:59 |
| Reporter | Kaj Ekman | Assigned To | THuber | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 2.40 (First JVCS release) | ||||
| Target Version | Fixed in Version | 2.40 Stable (Server) | |||
| Summary | 0001187: IB express version of server not committing changes until shutted down | ||||
| Description | Did exprience a 4 week rollback of source-code after power failure. "CommitRetaining" doesn't actually commit changes to database. FIB version don't have this proplem. Tested both versions after crash. | ||||
| Tags | No tags attached. | ||||
| Fix in JVCS version | |||||
| Releasedocumentation | |||||
|
|
Just two questions for clarification of the server/database environment/settings: 1) Was it a Firebird(?) server on a windows machine? 2) Was the database set to 'write thru' (gfix -write sync)? |
|
|
1) Interbase 7.0.1.1 on Windows 2000 Server 2) Old database converted from Interbase 5.6 to 7.1 don't know if that affects Write Sync. Not a single COMMIT during 4 weeks time with IBX version. Data was commited only when service was shutdown. I compiled the same source with FIB 4.81 and every change we made to database was commited right away. (Delphi 7 in use). Simulated even powerfailures. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-03-05 13:29 | THuber | Status | acknowledged => resolved |
| 2004-03-05 13:29 | THuber | Resolution | open => fixed |
| 2004-03-05 13:29 | THuber | Assigned To | => THuber |
| 2005-01-15 05:51 | THuber | Relationship added | child of 0002361 |
| 2005-06-13 16:59 | THuber | Status | resolved => closed |
| 2005-06-13 16:59 | THuber | Fixed in Version | => 2.40 Stable (Server) |
