Subject Re: Firebird Query Problem
Author bk007121
--- In firebird-support@yahoogroups.com, Svein Erling Tysvær
<svein.erling.tysvaer@k...> wrote:
>
> --- In firebird-support@yahoogroups.com, "bk007121" wrote:
> > --- In firebird-support@yahoogroups.com, Helen Borrie wrote:
> > > >WHERE
> > > >GRPLIST.GROUP_ID=ITMLIST.GROUP_ID
> > > >AND
> > > >ITMLIST.ITEM_ID=1
>
> > > FROM
> > > ITMLIST IL JOIN GRPLIST GL
> > > ON
> > > GL.GROUP_ID=IL.GROUP_ID
> > > WHERE
> > > IL.ITEM_ID=1
> >
> > Looks like I was a bit of a smartarse in my last reply (which has
> > since been removed).
>
> Huh? That's the first time I've seen anyone remove something from this
> list - I didn't know it was possible, but I do think I read your reply
> when it was available.
>
> > I tried your query as said before, but it didn't fix the problem
> > either. I though the increase in buffer size did fix it, but i made
> > a mistake and ran an amended query that had fields removed, which is
> > why it worked.
>
> The one thing I noticed from your original reply, was that you said
> you changed from implicit to explicit joins, but you didn't mention
> anything about changing what was the main point of Helen's reply. In
> your original query, you used the alias in the SELECT clause, but the
> table name in the WHERE clause - whereas Helen wanted you to use the
> alias in both cases.
>
> Anyway, maybe you should give some more information? E.g. table and/or
> view definition (are the 'TEXT' fields huge varchars or something) and
> plan chosen. Do you have sufficient space for any temporary files and
> have you checked your database for corruption etc?
>
> Set

Hey Set,

I actually removed the reply, because the information in it was plain
wrong, so I didn't want to confuse anyone.

I regards to Helen's reply, I have actually tried both, Helens'
suggestion (changing the alias use in the WHERE clause) and also used
Helens query which already has this method in place.

The TEXT_ field in the table are actually fairly huge varchars (8000),
which might seem bad, but I have seen a project use the same database
structure before (just less varchar field in the items table) and it
worked fine.

I will try to see if changing the fields to some smaller varchar, or
maybe BLOB or TEXT will solve the problem.

I also checked with the server admin and there seems to be enough temp
space available.

Thanks for the hints.

Ben