[eclipselink-dev] SVN trunk commit: Bug#349349 - force drop tables

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipselink-dev] SVN trunk commit: Bug#349349 - force drop tables

From: James Sutherland <JAMES.SUTHERLAND@xxxxxxxxxx>
Date: Tue, 14 Jun 2011 11:55:16 -0700 (PDT)
Delivered-to: eclipselink-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-dev>
List-help: <mailto:eclipselink-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=unsubscribe>

SVN trunk commit: Bug#349349 - force drop tables

https://bugs.eclipse.org/bugs/show_bug.cgi?id=349349

Changes:

- Changed TableCreator dropTables to attempt 5 times until all tables are successfully dropped

- change replaceTables to call drop and then create

- disable logging errors when dropping tables unless <= fine

- SchemaManager.FORCE_DROP flag to disable 5 trys

- changed Vector to List for TableCreator tables

- Added JPA2 performance tests

Prev by Date: Re: [eclipselink-dev] Archiving old releases... (Indigo Finaldaze)
Next by Date: [eclipselink-dev] BUILD STATUS:: trunk nightly build has test failures!
Previous by thread: [eclipselink-dev] Archiving old releases... (Indigo Finaldaze)
Next by thread: [eclipselink-dev] Bug 302293 - Merging collection of unregistered new objects from managed object corrupts cache
Index(es):
- Date
- Thread

Back to the top