[
https://issues.apache.org/jira/browse/OPENJPA-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329451#comment-17329451
]
Mark Struberg commented on OPENJPA-2808:
----------------------------------------
Hi [~solomax] !
While creating a unit test for this scenario I figured that we likely do not
want to create an explicit {{DROP INDEX}}. Usually an Index is bound to a
table. This is explicitly the case for {{@Index}} in the {{@Table}} annotation.
And when you drop the table, the index will also automatically get discarded.
Which means we do not need to take care about those Indexes, isn't?
> SchemaTool action DROP doesn't drop Indexes created with @Index
> ---------------------------------------------------------------
>
> Key: OPENJPA-2808
> URL: https://issues.apache.org/jira/browse/OPENJPA-2808
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 3.1.1
> Reporter: Mark Struberg
> Assignee: Maxim Solodovnik
> Priority: Major
> Fix For: 3.1.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When using {{@Index(name="IFK_SOMEFK",...}} we should also drop this when
> generating the DROP statement with our SchemaTool.
> e.g. when setting
> {noformat}
> <plugin>
> <groupId>org.apache.openjpa</groupId>
> <artifactId>openjpa-maven-plugin</artifactId>
> <version>${openjpa.version}</version>
> <configuration>
> <sqlAction>drop</sqlAction>
> </configuration>
> </plugin>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
