Modify ↓

Ticket #957 (closed defect: fixed)

Opened 19 months ago

Last modified 18 months ago

Oracle DROP TABLE should not PURGE (not compatible with 9i)

Reported by: Sam Hartsfield <samh.public@…> Owned by: andrew
Priority: minor Milestone: 1.0
Component: databaseapi Version: mercurial
Keywords: Cc:

Description

The "DROP TABLE PURGE" syntax is new in Oracle 10, so it gives an error if you're using Oracle 9. Patch is attached.

Attachments

remove_purge.diff​ (694 bytes) - added by Sam Hartsfield <samh.public@…> 19 months ago.

Change History

Changed 19 months ago by Sam Hartsfield <samh.public@…>

comment:1 Changed 19 months ago by andrew

  • Status changed from new to infoneeded
  • Priority changed from major to minor
  • Milestone set to 1.0

Is PURGE useful at all? There might be a reason to leave it in if you're using 10 or higher - I'm not familiar enough with Oracle to know, though.

comment:2 Changed 18 months ago by Sam Hartsfield <samh.public@…>

  • Status changed from infoneeded to assigned

Apparently in Oracle 10, a deleted table will go in the "recycle bin", unless you add "PURGE" (the recycle bin didn't exist in Oracle 9).

Our DBA suggested that it would be best to leave off the PURGE even in Oracle >= 10, in case you made a mistake and wanted to restore it.

comment:3 Changed 18 months ago by andrew

  • Status changed from assigned to closed
  • Resolution set to fixed

Cool - committed as [546f9bbf06b6]. Thanks.

comment:4 Changed 18 months ago by Sam Hartsfield <samh.public@…>

It doesn't look like that changeset made it into the main repository.

comment:5 Changed 18 months ago by andrew

Yep, guess who forgot to run hg push.

View ↑

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.