Avoid unnecessary flushes on table operations that don't require it (e.g. truncate, possibly rename, etc)

Registered by Vladimir Kolesnikov on 2010-12-07

Currently for table operations like TRUNCATE the table is being flushed to disk and then closed. In this case flushing is not needed as we're going to drop the data anyway... Another case is when the table is closed-renamed-opened - in this case it's likely we can avoid flushing as well...

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.