I've been having a number of problems with a schema which includes
multiple / nested main tables. It seems a naive build will build
filters which all refer to 'main' instead of the full table name and
when generating SQL will request columns from 'main' but only create
the alias from the last table added to TableSet.pm.
Sorting this out in one dataset was just a matter of replacing all the
tableConstraint: main values with their fullname equivalents, but in
another this hasn't worked and I'm a bit stumped as to why. Could you
give me more info about how this 'main' table is defined and anywhere
else I could look to resolve it.
thanks
-s
--
Seth Redmond
Scientific Programmer, VectorBase
Kafatos / Christophides Groups
Div. Cell and Molecular Biology
Imperial College, London
[EMAIL PROTECTED]
--
