On 6 Mar 2007, at 14:22, seth redmond wrote:
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
Hi Seth,
the 'main' alias is there on purpose to allow SQL compiler
to dynamically choose a 'path' through the schema dependent
on your attribute and filter choices ei choosing the right main
table for each individual query. Changing it to fully qualified names
for the 'single main table' dataset should work but for a 'multiple
main table' one
probably wont.
Could you give us more details on your schema and tell us exactly why
this is causing you problems?
cheers,
a.
-s
--
Seth Redmond
Scientific Programmer, VectorBase
Kafatos / Christophides Groups
Div. Cell and Molecular Biology
Imperial College, London
[EMAIL PROTECTED]
--
------------------------------------------------------------------------
-------
Arek Kasprzyk
EMBL-European Bioinformatics Institute.
Wellcome Trust Genome Campus, Hinxton,
Cambridge CB10 1SD, UK.
Tel: +44-(0)1223-494606
Fax: +44-(0)1223-494468
------------------------------------------------------------------------
-------
