"Gary Benade" <gary@...> wrote:

>
> select coalesce( mc.catagory, 'Other') catagory, c.menucode, i.menuitem,
> i.uniquelink, i.price, n.note, c.vegetarian, c.kosher, c.halal, c.health,
> c.kids from menucode c inner join menuitems i on c.link = i.link and
> i.deleted = 'N' left outer join meal_catagory mc on c.mealcatagory =

mc.link

> and mc.deleted = 'N' left outer join menunotes n on n.menucodelink =

c.link

> and n.deleted = 'N' where c.available = 'Y' and c.restlink = 'BEN0000059'
> and c.deleted = 'N' PLAN SORT (JOIN (JOIN (C INDEX (I_MENUCODE_RESTLINK),I

> INDEX (MENUITEMS_MENUCODELINK)),N INDEX (RDB$PRIMARY24))) order by 1,
> c.menucode, i.menuitem, i.price
>
> ibase_errmsg: table MEAL_CATAGORY is not referenced in plan

Plan is not a hint. You should specify access path for all the tables
references in the statement. Previous FB versions were more ignorant in
regard of many things, but now the engine becomes stricter. Generally it's
considered to be a good thing (tm), but sometimes it also causes upgrade
issues. That's life :-)

> I also got the following message in the web log:
>
> INSERT INTO WEB_LOG( SESSIONID, CUSTOMERLINK, RECDATE, RECTIME, PAGENAME,
> IP) VALUES
>

('3sgrdpipfuo9tu4tlb5emd15h6','',current_date,current_time,'browsemenus.php'
,'163.195.192.74')

>
> ibase_errmsg: internal gds software consistency check (invalid SEND

request

> (167), file: exe.cpp line: 494)

Looks like a FB issue, so a test case would be much appreciated (before we
go for a final release and it's too late).

> The database is huge and I haven't gotten around to doing a backup/restore

> yet meaning the database is still ODS 10.1, could this be a problem?

Theoretically, it shouldn't be a problem. At least I don't see how it could
be related to an ODS version. But the engine is tested with ODS11 databases
only, so some older ODS related regression could be missed by the tests.
Hence we always recommend to upgrade to the newer ODS before putting
software into production.


Dmitry