> >
> > Instead of getting a list and looping through the list selecting

from

> > another table, select directly from a join between the two tables,

which

> > presumably are connected by a foreign key.
> > Can you post the DDL for the two tables, including foreign keys and
> > indexes, and the plan used by the optimizer?
>
> I've tried to do an inner join before but I get a kernel error through
> Python (from vm_allocate() method) in my Mac system. This issue had
> been documented and Python does not have vm_allocate() method in its
> codes. Which is why I used this workaround to get all my records.
>

Yuck!

That precludes a fair wack of optimisation right there. As a work
around to this apparent problem with Python, could you possibly then
create a selectable stored procedure or view that internally did the
join for you?

It seems like a pretty concerning bug if you can not execute a query
with a join, so I would also double check that this is in fact the
case, is there a FB/Python list?

Adam