Closed GoogleCodeExporter closed 8 years ago
What would the use case be for separating out two different data series for the
same
instrument? I'm more comfortable adding the ability to save series to a flat
file
and delete a series from the DB, that way users can manage what is in the DB
however
they wish without adding in hacks to the data model.
The duplicate data issue can be solved in a few ways. If we want to be simple,
we
could add a unique() constraint to the BAR table as:
unique(bar_series_id, timespan_id, begin_time)
To modify an existing DB, the syntax is:
alter table bar add unique(bar_series_id, timespan_id, begin_time);
The downside is that it generates an SQL Exception for each duplicate row which
is
slooooow to process. I made these changes, but wouldn't mind having a better
solution. Does anyone have any suggestions for how to check for duplication in
a
more efficient fashion?
Original comment by tyrotra...@gmail.com
on 30 May 2007 at 10:26
Original issue reported on code.google.com by
damiaan....@econ.kuleuven.be
on 30 May 2007 at 7:54