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!feeder1.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Java DB rotation Date: Tue, 31 Jan 2012 08:38:42 +0100 Lines: 46 Message-ID: <9opk4aFpfhU2@mid.individual.net> References: <4f2752d1$0$283$14726298@news.sunsite.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: individual.net dTl3ym/mF2WUi5FYDBqGIg9ugh6DbWoBQ0IJ/nIHwL244Iy9c= Cancel-Lock: sha1:oLyka5Ijbo3+QFaLafIiiZ2lEDg= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 In-Reply-To: <4f2752d1$0$283$14726298@news.sunsite.dk> Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:11672 On 31.01.2012 03:32, Arne Vajh=F8j wrote: > On 1/30/2012 9:24 PM, Jim Lee wrote: >> On Tue, 31 Jan 2012 02:21:11 +0000 (UTC), Martin Gregorie >> wrote: >>> 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/mon= day >>>> e.g. >>>> table-1-2-2012 table-1-9-2012 table-1-16-2012 table-1-23-2012 ... et= c >>>> >>> What problem are you using table rotation to solve? >>> >>> What would prevent you from using a single table containing datestamp= ed >>> rows which are archived and/or deleted the rows after "cycle length" >>> days? >> >> my main problem is how to make sure "how to get the correct table name= >> to read/write to" depending what day in the week >> >> start a new DB table is a must since it's going through some other >> REST backend layer > > There is nothing in REST that requires such a table structure. > > And it would be better to fix the bad code requiring such > a table rollover than to make other apps bad to work with it. Another question: Jim, what database are you using? If the instance=20 requiring multiple tables is afraid of volume the typical solution to=20 this issue is called "partitioning". If your database supports it,=20 that's typically the way to go for such kind of data. Cheers robert --=20 remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/