Subject | Re: [firebird-support] Re: DDL updates in 2.5 |
---|---|
Author | Mark Rotteveel |
Post date | 2011-11-21T09:06:49Z |
On Mon, 21 Nov 2011 08:59:30 -0000, "martin.agren"
<martin_gbg_@...> wrote:
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.
<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 clientapp)
> and am not getting the desired results as data is unchanged. I makeanother
> change, still no effect. Then, when disconnectiong and restarting myclient
> side apps all the changes suddenly appear.If you are using Classic that is - as far as I know - a known issue. Every
>
> Very frustrating.. :)
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.