Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow write operations to temporary tables in read only databases [CORE1325] #1744

Open
firebird-automations opened this issue Jun 16, 2007 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @asfernandes

Relate to CORE3399

Votes: 5

As temporary tables could be used for read operations, for example calculations in SPs, and they never write to the main file, should be very desirable if they work in read only databases.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Horsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 12340 ] => Firebird [ 14879 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pmakowski

not only read only databases but also read only transaction

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue relate to CORE3399 [ CORE3399 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Temporary tables with ON COMMIT DELETE option is writable (in read only databases) as side effect of implementation of CORE3399.

To make temporary tables fully writable in read only databases we need some way to account transaction states at least at attachment level, i.e. track active\committed transactions of given attachment and track "local" OIT and OST numbers.
This is task for the (probably near) future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants