Hi Jason

I don't know if I need the temp tables to show in he cache. I do use
them so I guess so. I suppose what I am after is a partial refresh. i.e.

a) create new table
b) Add new table details to existing schema
c) Access table

as opposed to the current situation (I think)

a) create new table
b) Access (any) table, Entire schema is refreshed
c: Access table

Hope this helps your understanding of the situation :)

Rob Martin
Software Engineer

phone +64 03 377 0495
fax +64 03 377 0496
web www.chreos.com

Wild Software Ltd



Jason Wharton wrote:

>> A number of people have made suggestions about not creating
>> multiple temp tables, however my issue is the performance
>> hit I take every time I run a DDL statement (when Ibo needs
>> to update its cache).
>> Do you have any suggestions ?
>>
>
> Do you need those temp tables to show up in the cache?
>
> You should be able to customize the schema cache getting updated so that it
> won't trigger a resynch.
>
> Jason
>
>
>> -----Original Message-----
>> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
>> Behalf Of Robert martin
>> Sent: Tuesday, May 15, 2007 1:44 PM
>> To: IBObjects@yahoogroups.com
>> Subject: Re: [IBO] performance issue when adding tables
>>
>>
>> Hi Jason
>>
>> I posted the following a while ago. I am just reposting it
>> in case you
>> missed it.
>> Rob Martin
>> Software Engineer
>>
>> phone +64 03 377 0495
>> fax +64 03 377 0496
>> web www.chreos.com
>>
>> Wild Software Ltd
>>
>>
>>
>> Robert martin wrote:
>>
>>> Hi
>>>
>>> We have a screen in our app that creates tables (DDL) to use on a
>>> temporary basis. As FB doesn't yet support temp tables we
>>>
>> are handling
>>
>>> the removal of said tables. However we don't do it well.
>>>
>> This leads to
>>
>>> us having a large number of unused tables in our DB at times (we do
>>> eventually remove them). However this is not the main
>>>
>> issue, it just
>>
>>> compounds it.
>>>
>>> IBO collects a schema of the db and whenever DDL changes
>>>
>> take place the
>>
>>> schema gets completely regenerated. This is a real problem
>>>
>> for us as it
>>
>>> adds a large amount of delay after creating a new temp
>>>
>> table. I believe
>>
>>> this is an issue regardless of whether or not the schema is
>>>
>> cached (we
>>
>>> don't cache). The large number of tables makes this
>>>
>> process quite slow
>>
>>> (seconds ?)
>>>
>>> In the help it says I might be able to use executeImmediate
>>>
>> to do the
>>
>>> ddl without forcing a rebuild of the schema. However my
>>>
>> guess is that
>>
>>> if I do this than IBO won't 'see' the newly created temp
>>>
>> table (that I
>>
>>> need to use).
>>>
>>> Does anyone have a suggestion as to how to get around this?
>>>
>>>
>>>
>> ______________________________________________________________
>> _____________
>> IB Objects - direct, complete, custom connectivity to
>> Firebird or InterBase
>> without the need for BDE, ODBC or any other layer.
>> ______________________________________________________________
>> _____________
>> http://www.ibobjects.com - your IBO community resource for
>> Tech Info papers,
>> keyword-searchable FAQ, community code contributions and more
>> !
>> Yahoo! Groups Links
>>
>>
>>
>>
>
>
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>
>
>
>