Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: Java DB rotation Date: Tue, 31 Jan 2012 02:21:11 +0000 (UTC) Organization: UK Free Software Network Lines: 18 Message-ID: References: NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1327976471 8760 84.45.235.129 (31 Jan 2012 02:21:11 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Tue, 31 Jan 2012 02:21:11 +0000 (UTC) User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:11654 On Mon, 30 Jan 2012 18:08:04 -0800, Jim Lee wrote: > I have a Java server controller that read/write to Database table > > Java server will start read / write to a new DB table every week/monday > e.g. > table-1-2-2012 table-1-9-2012 table-1-16-2012 table-1-23-2012 ... etc > What problem are you using table rotation to solve? What would prevent you from using a single table containing datestamped rows which are archived and/or deleted the rows after "cycle length" days? -- martin@ | Martin Gregorie gregorie. | Essex, UK org |