> --- In firebird-support@yahoogroups.com, Mark Rotteveel<mark@...> wrote:
>>
>> On Mon, 21 Nov 2011 08:59:30 -0000, "martin.agren"
>> <martin_gbg_@...> wrote:
>>> Data output from my stored proc isnt reflecting the changes I have made.
>> I
>>> make changes in DDL, check the "new" dataset (Flamerobin or my client
>> app)
>>> and am not getting the desired results as data is unchanged. I make
>> another
>>> change, still no effect. Then, when disconnectiong and restarting my
>> client
>>> side apps all the changes suddenly appear.
>>>
>>> Very frustrating.. :)
>>
>> If you are using Classic that is - as far as I know - a known issue. Every
>> connection has its own metadata cache, so DDL changes are not always
>> directly visible to other connections. Therefor it is usually advisable to
>> execute DDL in isolation. Why are you executing DDL as part of - I assume
>> - your normal application execution? It is usually advisable not to change
>> the database layout as part of the your application execution and only
>> change it when upgrading to a newer version of the application.
>>
>
> Hi,
>
> No, I am using SS. And the DDL changes are never changed as part of application execution. But when developing, i often work from both Flamerobin and my app to see effects of metadata changes.

Can you provide a re-producable test case with e.g. a simple script
executable in isql?

This still sounds a bit like a transaction issue.



--
With regards,
Thomas Steinmaurer

* Upscene Productions - Database Tools for Developers
http://www.upscene.com/

* My Blog
http://blog.upscene.com/thomas/index.php

* Firebird Foundation Committee Member
http://www.firebirdsql.org/en/firebird-foundation/