🚀 go-pugleaf

Hi Jose,

You might want to try with IB 6.5 or 7 when the download comes available.


--

With regards,

Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."

> IB 6.0.2.0.
> the same happens with 6.0.1.0 too.
>
> thanks
>
> Jose Carlos
>
> "Martijn Tonies" <m.tonies@upscene_remove.com> escreveu na mensagem
> news:3df775a5$1@newsgroups.borland.com...
> > Hi,
> >
> > What version of IB are you using? I recall a bug in earlier versions
> > that messed up the PLAN that IB returned.
> >
> >
> > --
> >
> > With regards,
> >
> > Martijn Tonies
> > InterBase Workbench - the developer tool for InterBase & Firebird
> > Firebird Workbench - the developer tool for Firebird
> > Upscene Productions
> > http://www.upscene.com
> >
> > "This is an object-oriented system.
> > If we change anything, the users object."
> >
> > >
> > >   I Have the following tables and view :
> > >
> > > CREATE TABLE TAB1
> > > (
> > >   COD INTEGER NOT NULL,
> > >   DESCR VARCHAR(10),
> > >   CODTAB INTEGER,
> > >   TYPETAB VARCHAR(1)
> > > );
> > >
> > > CREATE TABLE TAB2
> > > (
> > >   COD INTEGER NOT NULL,
> > >   DESCR VARCHAR(10)
> > > );
> > >
> > > CREATE TABLE TAB3
> > > (
> > >   COD INTEGER NOT NULL,
> > >   DESCR  VARCHAR(10)
> > > );
> > >
> > > CREATE VIEW V_TABS
> > > (
> > >   COD,
> > >   DESCR,
> > >   TYPETAB
> > > )
> > > AS
> > > SELECT
> > >   COD,
> > >   DESCR,
> > >   '2'
> > >   FROM
> > >     TAB2
> > >
> > > UNION
> > >
> > > SELECT
> > >   COD,
> > >   DESCR,
> > >   '3'
> > >   FROM
> > >     TAB3;
> > >
> > >
> > >   My problem happens when I try to run the following
> > > select :
> > >
> > > SELECT
> > >     TAB1.COD,
> > >     TAB1.DESCR,
> > >     TAB1.TYPETAB || ' - ' || V_TABS.DESCR
> > >   FROM
> > >     TAB1
> > >     LEFT OUTER JOIN V_TABS
> > >     ON (  (V_TABS.CODTAB = TAB1.CODTAB)
> > >         AND
> > >           (V_TABS.TYPETAB = TAB1.TYPETAB))
> > >
> > >   The select return the records I want but my plan analyser tool goes
> crazy
> > > and show a lot of unrecognized characters instead of the correct plan.
> Am I
> > > doing something wrong ? Can I trust that my select will always work ?
> > >
> > > Is there some problem using a VIEW based on a UNION of two SELECT's ? Is
> it
> > > safe ?
> > >
> > > Do you have some other idea ?
> > >
> > > Thanks for reading.
> > >
> > > Jose Carlos
> > > Brazil
> > >
> > >
> >
> >
>
>