Currently, DerbyTable classes are too generic because they are not associated
with a tuple storage/DB schema type. It would help if each DerbyTable class had
a generic parameter that specified the kind of Tuple the table contains. This
would also help our design by keeping tuple/schema information in a single
object, which we can then operate on.
For this task, first create an abstract Tuple class. This class will maintain a
reference to a DerbyTable, and maybe a few other things later on.
Next, subclass Tuple to create a class for every DerbyTable, e.g.,
VisitorTuple. Each Tuple subclass should contain data members that represent an
actual DB tuple.
Finally, parametrize all existing DerbyTable classes with the corresponding
Tuple types.
Original issue reported on code.google.com by bestchai on 8 Mar 2012 at 7:01
Original issue reported on code.google.com by
bestchai
on 8 Mar 2012 at 7:01