Hi Helen,
I'm new to this News-Group and would like to expand and add to the
questions already posed.

--- In ib-support@y..., Helen Borrie <helebor@d...> wrote:
> At 10:49 AM 23-03-01 +0700, you wrote:
> >Hi, All
> >I am working with Interbase for many application (especially Web
Applicaton),and
> >The Performance is good.
> >I want to ask about the Temporary Table, How to declare ???, and
can Temporary table inserted using coomand Inset into .... values
.......
> >Because I've to use to use Temporary table in My application
> >
>
> Creating temporary tables is rarely necessary with InterBase
(unlike
>e.g. MSSQL, which has no other means to generate a multi-row result
>set from a stored proc.)


I don't fully understand this. Does this mean that IB/FB have an
alternate way of chaining queries. What I'm saying is normally I
would
perform an SQL and create a result set which I would then save in a
temporary table to be used as the input to another query. The only
alternative that I can see is to build HUGE (and unmaintainable) SQL
statements. The question is then, do I do this differently in IB/FB.


>It's also a bad idea in a transactional
>RDBMS to have users creating and destroying objects.


Could you please elaborate? I would really like to know your
reasoning
on this one - it is a security concern, a performance concern or
something else?


> If you don't need to bring the temporary data to the user
interface,
>don't have a Temp table at all. In InterBase, you can perform table
>updates that read data from one or more tables in one or more other
>tables using a stored procedure, without creating an intermediate
>on-disk structure at all, using the FOR SELECT...INTO...DO construct.


Is there any way of doing this without creating a stored procedure?


Helen,
I have an additional question which is somewhat related to temporary
tables. If I create an SQL statement using a "LEFT OUTER JOIN" on
two
tables and therefore end up with NULL values in some of my fields in
my result set, what happens if I use that result set to join to yet
another table on a field with possible NULL values. Does a join on a
field with a NULL value always return an emtpy result set, or do I
get
all the rows that meet the NULL criteria.


I am very new to Interbase and am currently evaluating it as a
replacement for MS-SQLServer, so you can imagine that I am keen to
work out all the issues that may confront me before making the switch.


Thankyou and Regards

John Vander Reest.