Re: Java DB rotation
- From: Arne Vajhøj <arne@xxxxxxxxxx>
- Date: Tue, 31 Jan 2012 20:31:37 -0500
On 1/31/2012 1:57 PM, Chris Riesbeck wrote:
On 1/31/2012 1:38 AM, Robert Klemme wrote:On 31.01.2012 03:32, Arne Vajhøj wrote:On 1/30/2012 9:24 PM, Jim Lee wrote:On Tue, 31 Jan 2012 02:21:11 +0000 (UTC), Martin Gregorie
On Mon, 30 Jan 2012 18:08:04 -0800, Jim Lee wrote:I have a Java server controller that read/write to Database tableWhat problem are you using table rotation to solve?
Java server will start read / write to a new DB table every
table-1-2-2012 table-1-9-2012 table-1-16-2012 table-1-23-2012 ... etc
What would prevent you from using a single table containing
rows which are archived and/or deleted the rows after "cycle length"
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
requiring multiple tables is afraid of volume the typical solution to
this issue is called "partitioning". If your database supports it,
that's typically the way to go for such kind of data.
Pretty much every response from the OP has suggested either really bad
intra-team communication (distributed team?), or a system architect
angling for an appearance on the Daily WTF.
In both cases it would make sense to push back a little
(within the constraints given by the org chart)
- Prev by Date: Re: Java DB rotation
- Next by Date: Re: Java DB rotation
- Previous by thread: Re: Java DB rotation
- Next by thread: Re: Java DB rotation