Subject | Re: DDL updates in 2.5 |
---|---|
Author | martin.agren |
Post date | 2011-11-21T09:10:56Z |
--- In firebird-support@yahoogroups.com, Mark Rotteveel <mark@...> wrote:
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.
>Hi,
> 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.
>
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.