This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:features:segments:dropping [2012/03/05 21:43] doc |
admin:features:segments:dropping [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| ==== Dropping Segments ==== | ==== Dropping Segments ==== | ||
| - | Omnidex Segments can be dropped, resulting in the removal of the object from the connection, and also the removal of the underlying data. Omnidex Segments are dropped using the [[dev:sql:statements:drop_segment:home|DROP SEGMENT]] statement, as shown in the example below: | + | Omnidex Segments can be dropped, resulting in the removal of the object from the connection, and also the removal of the underlying data. It is not required to drop segments, as they will be automatically dropped when the connection ends. Dropping segments is required when reusing the same connection name within the same connection. |
| + | |||
| + | Omnidex Segments are dropped using the [[dev:sql:statements:drop_segment:home|DROP SEGMENT]] statement, as shown in the example below: | ||
| <code> | <code> | ||