Does anyone have insight into how the "import" would compare to the "drop/recreate" workaround, performance-wise? I'm currently using drop/recreate for a large number of tables, so just wondering if it would be worth trying import.
Regarding holding up the truncate feature because of lack of standards, an interim solution could be to use a system procedure similar to the way import is implemented. I realize that's not the only thing holding up the feature... it also needs a volunteer. ;) Jim > -----Original Message----- > From: fancellu [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 19, 2008 11:57 PM > To: [email protected] > Subject: Re: Any ETA on "truncate table" ? > > > Unfortunately I don't have the free time to help the project, I have > enough > of my own fish to fry. > > However, as a work around, I've found it much quicker to simply drop the > table and then recreate it with the same name. > > e.g. > > Statement stat=conn.createStatement(); > stat.executeUpdate("DROP TABLE PKS"); > stat.executeUpdate("CREATE TABLE PKS ( PK varchar(32) PRIMARY KEY > NOT NULL )" ); > conn.commit(); > > -- > View this message in context: http://www.nabble.com/Any-ETA-on- > %22truncate-table%22---tp15562346p15585747.html > Sent from the Apache Derby Users mailing list archive at Nabble.com. >
