QualityCentral

Public Report

Report From: InterBase/Server/Internal [ Add a report in this area ]

Report #: 47599

Status: Closed

(Pulled) Data inserted in the last transaction not seen if the database is made read only. Workaround on existing database: 1. Make d

Project: InterBase

Build #: 7.5.1.80

Version: 7.5

Submitted By: QC<->Raid Replicator Account

Report Type: Crash / Data loss / Total failure

Date Reported: 9/23/2005 12:00:00 AM

Severity: Infrequently encountered problem

Last Updated: 10/2/2007 4:39:08 PM

Platform: All platforms

Internal Tracking #: 231879

Resolution: Fixed (Resolution Comments)

Resolved in Build: : 7.5.1.113

Duplicate of: None

Voting and Rating

Overall Rating: No Ratings Yet

0.00 out of 5

Total Votes: None

Description

Data inserted in the last transaction not seen if the database is made read only.

Workaround on existing database:
1. Make database read-write
2. Stand and commit one transaction
3. Make it be read-only again

Workaround to make it not happen:
Ater committing all data, start and commit one more transaction before making the database read only.

>>>
20-Jan-2006 bug council
Quinn says this issue was caused by the transaction ID being same for all RO transactions fix done for CarlZeiss. Look into incrementing TID by one and use that for RO databases.
<<<

Steps to Reproduce:

1. Open project1.exe which is attached.
2. Click button - row 15 gets added.
3. Use gfix to make the database read_only
4. Open database with isql, select * from t. Row 15 does not display
5. Use gfix to the make the database read_write again
6. Open database with isql. select * from t. Row 15 now displays.

you can reclick the button in this application multiple times, and everytime it will insert a new incremented row value

Workarounds

None

Attachment

Comments

None

Quality Central

Developer Tools

Database Tools